<html><head><meta http-equiv="Content-Security-Policy" content="script-src 'self'; img-src * cid: data:;"><style id="outgoing-font-settings">#response_container_BBPPID{font-family: initial; font-size:initial; color: initial;}</style></head><body style="background-color: rgb(255, 255, 255); background-image: initial; line-height: initial;"><div id="response_container_BBPPID" style="outline:none;" dir="auto" contenteditable="false"> <div name="BB10" id="BB10_response_div_BBPPID" dir="auto" style="width:100%;">Just read the phab discussion. If I misunderstood the situation, please correct me. </div><div name="BB10" id="BB10_response_div_BBPPID" dir="auto" style="width:100%;"><br></div><div name="BB10" id="BB10_response_div_BBPPID" dir="auto" style="width:100%;">Wondering where the original discussion happened where 'we' decided to merge two orthogonal concepts into one. Can you point me to the relevant thread on plasma-devel?</div><div name="BB10" id="BB10_response_div_BBPPID" dir="auto" style="width:100%;"><br></div><div name="BB10" id="BB10_response_div_BBPPID" dir="auto" style="width:100%;">If this is about providing a unified implementation in kwin for both VDs and activities, I'm fine with that. If not, then continue reading. </div><div name="BB10" id="BB10_response_div_BBPPID" dir="auto" style="width:100%;"><br></div><div name="BB10" id="BB10_response_div_BBPPID" dir="auto" style="width:100%;">VDs are for managing windows - a solution for the 'I don't have a screen large enough for all these windows'.</div><div name="BB10" id="BB10_response_div_BBPPID" dir="auto" style="width:100%;"><br></div><div name="BB10" id="BB10_response_div_BBPPID" dir="auto" style="width:100%;">Activities are for managing work - a solution to the 'I don't want documents/files/etc. from separate projects to get jumbled up together'.</div><div name="BB10" id="BB10_response_div_BBPPID" dir="auto" style="width:100%;"><br></div><div name="BB10" id="BB10_response_div_BBPPID" dir="auto" style="width:100%;">Previously, we had problems when we tried to equate activities with any specific thing. As in, 'an activity is a group of Plasma widgets'. The same will happen if the activity becomes 'a group of windows'.</div><div name="BB10" id="BB10_response_div_BBPPID" dir="auto" style="width:100%;"><br></div><div name="BB10" id="BB10_response_div_BBPPID" dir="auto" style="width:100%;">This has been discussed quite a few times before. </div><div name="BB10" id="BB10_response_div_BBPPID" dir="auto" style="width:100%;"><br></div><div name="BB10" id="BB10_response_div_BBPPID" dir="auto" style="width:100%;">Has anyone collected the use-cases of activities before coming up with this idea?</div><div name="BB10" id="BB10_response_div_BBPPID" dir="auto" style="width:100%;"><br></div><div name="BB10" id="BB10_response_div_BBPPID" dir="auto" style="width:100%;">Cheers, </div><div name="BB10" id="BB10_response_div_BBPPID" dir="auto" style="width:100%;">Ivan </div><div name="BB10" id="BB10_response_div_BBPPID" dir="auto" style="width:100%;"><br></div><div name="BB10" id="BB10_response_div_BBPPID" dir="auto" style="width:100%;"><br></div> <div name="BB10" id="response_div_spacer_BBPPID" dir="auto" style="width:100%;"> <br style="display:initial"></div> <div id="blackberry_signature_BBPPID" name="BB10" dir="auto"> <div id="_signaturePlaceholder_BBPPID" name="BB10" dir="auto">Sent via the <a href="http://play.google.com/store/apps/details?id=com.blackberry.hub">BlackBerry Hub for Android</a></div> </div></div><div id="_original_msg_header_BBPPID" dir="auto"> <table width="100%" style="background-color: white; border-spacing: 0px; display: table; outline: none;" contenteditable="false"><tbody><tr><td colspan="2" style="padding: initial; font-size: initial; text-align: initial; background-color: rgb(255, 255, 255);"> <div style="border-right: none; border-bottom: none; border-left: none; border-image: initial; border-top: 1pt solid rgb(181, 196, 223); padding: 3pt 0in 0in; font-family: Tahoma, "BB Alpha Sans", "Slate Pro"; font-size: 10pt;"> <div id="from"><b>From:</b> mvourlakos@gmail.com</div><div id="sent"><b>Sent:</b> 3 July 2018 5:36 pm</div><div id="to"><b>To:</b> plasma-devel@kde.org</div><div id="reply_to"><b>Reply to:</b> plasma-devel@kde.org</div><div id="subject"><b>Subject:</b> Discussion for Virtual Desktops and Activities future</div></div></td></tr></tbody></table> <br> </div><!--start of _originalContent --><div name="BB10" dir="auto" style="background-image: initial; line-height: initial; outline: none;" contenteditable="false"><div dir="ltr"><div>A discussion started by me at: <a href="https://phabricator.kde.org/D13745">https://phabricator.kde.org/D13745</a> about concerns related to future Activities / Virtual Desktops merge (I will call it MERGE in the future). As proposed the discussion can be moved here.<br></div><div><br></div><div></div><div>In my opinion having a concrete draft how things are going to work from a user point view it might bring design issues that can be solved earlier than later. My opinion in the matter can be found at: <a href="https://psifidotos.blogspot.com/2012/03/activities-and-workareas-draft.html">https://psifidotos.blogspot.com/2012/03/activities-and-workareas-draft.html</a></div><div><br></div><div>1. I think that the previous draft can be used in order to identify any users workflow breakage from MERGE.</div><div>2. A new draft describing MERGE from a user point of view should be created in order for everyone (plama team and VDG) to understand what they are trying to create.<br></div><div><br></div><div><br></div><div>By reading comments I identified a internal decision in order for MERGE to be based more in Activites infrastructure for Plasma product and to VDs infrastructure for KWin product. I would propose to forget the technical approach and focus more on the user point of view. This could help avoid the VDs/Activities debate that started in Plasma 4/5 era and it is still present at a smaller degree.<br></div><div><br></div><div><br></div><div>I will start with one concern based on the comments I read even though it would be better for everyone to describe first what is expecting from the MERGE.</div><div><br></div><div><br></div><div>Concern [A]</div><div><br></div><div>If MERGE creates a new Activity each time the user needs more space for its windows, doesnt that break totally the VDs users workflow? <br></div><div><br></div><div>Example: <span class="gmail-transaction-comment">I am working on my current actitivity and I am writing a note in a plasma widget. I am creating a new Activity, should that Activity look the same as the previous one and if I change the note in the first should it look the same and in the second? (at this example a current VDs user would answer should be in sync and always the same, a current<br>
Activity user would answer it doesnt matter, it is unrelated)</span></div><div><span class="gmail-transaction-comment"><br></span></div><br><div><br></div></div>
<!--end of _originalContent --></div></body></html>