<table><tr><td style="">mvourlakos added a comment.
</td><a style="text-decoration: none; padding: 4px 8px; margin: 0 8px 8px; float: right; color: #464C5C; font-weight: bold; border-radius: 3px; background-color: #F7F7F9; background-image: linear-gradient(to bottom,#fff,#f1f0f1); display: inline-block; border: 1px solid rgba(71,87,120,.2);" href="https://phabricator.kde.org/D13745">View Revision</a></tr></table><br /><div><div><blockquote style="border-left: 3px solid #8C98B8;
color: #6B748C;
font-style: italic;
margin: 4px 0 12px 0;
padding: 8px 12px;
background-color: #F8F9FC;">
<div style="font-style: normal;
padding-bottom: 4px;">In <a href="https://phabricator.kde.org/D13745#286501" style="background-color: #e7e7e7;
border-color: #e7e7e7;
border-radius: 3px;
padding: 0 4px;
font-weight: bold;
color: black;text-decoration: none;">D13745#286501</a>, <a href="https://phabricator.kde.org/p/hein/" style="
border-color: #f1f7ff;
color: #19558d;
background-color: #f1f7ff;
border: 1px solid transparent;
border-radius: 3px;
font-weight: bold;
padding: 0 4px;">@hein</a> wrote:</div>
<div style="margin: 0;
padding: 0;
border: 0;
color: rgb(107, 116, 140);"><p>A lot of this is still up in the air, but here's the rough plan:</p>
<p>0. X11 will remain unchanged. The feature set of Activities will remain unchanged.</p>
<ol class="remarkup-list">
<li class="remarkup-list-item">For 5.14, we want to have virtual desktops working on Wayland, with feature parity to X11. Activities will not yet work on Wayland. The new Wayland protocol allows windows to be on more than one desktop and it allows for multiple concurrently active desktops, but these abilities will not be used in 5.14, they will only be present in the API (hence the API changes).</li>
<li class="remarkup-list-item">For 5.15, we want to sync Activities to virtual desktops on Wayland, meaning adding/removing Activities is how you add/remove virtual desktops, and switching/activating VDs==switching/activating Activities.
<br /><br />
That means on Wayland on 5.15+ (if this schedule holds) the default Task Manager would just hide all the virtual desktop UI, exposing only the activities UI.</li>
</ol></div>
</blockquote>
<p>I see...</p>
<p>The thing is that I can undestand the technical solution at some point but from user point of view I think that there will be issues.<br />
Personally I start from the user point of view how things will and should work and then I am focusing on the technical solution.</p>
<p>If I understood correctly VDs in the future will be Activities but without the extra space that someone might need for its windows.<br />
That will break the workflow for the VDs users who are the majority of the linux desktop<br />
(take note that I am not :). I am Activities heavy user that always uses one VD)).</p>
<p>If plasma devs agree on that roadmap then there are things that should be introduced in the future in order to make the VDs<br />
users life a bit easier.</p>
<p>e.g. When a new Activity will be created shouldnt look exactly as the active one and be always in sync with it?<br />
e.g. I am working on my current actitivity and I am writing a note on the desktop. I am creating a new Activity,<br />
should that Activity look the same as the previous one and if I change the note in the first to look the same and in<br />
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)</p>
<p>I fear that if this isnt orchestrated correctly with VDG a new debate for VDs and Activities <br />
will relaunch just like the plasma 4 and 5 debates for the matter.</p>
<p>You can read my personal opinion for the matter at: <a href="https://psifidotos.blogspot.com/2012/03/activities-and-workareas-draft.html" class="remarkup-link" target="_blank" rel="noreferrer">https://psifidotos.blogspot.com/2012/03/activities-and-workareas-draft.html</a><br />
I dont object in any alternative solution but the solution should be designed from<br />
the user point of view first and then starting implementing.</p></div></div><br /><div><strong>REPOSITORY</strong><div><div>R120 Plasma Workspace</div></div></div><br /><div><strong>REVISION DETAIL</strong><div><a href="https://phabricator.kde.org/D13745">https://phabricator.kde.org/D13745</a></div></div><br /><div><strong>To: </strong>hein, mart, mvourlakos<br /><strong>Cc: </strong>plasma-devel, ragreen, Pitel, ZrenBot, lesliezhai, ali-mohamed, jensreuterberg, abetts, sebas, apol, mart<br /></div>