https://bugs.kde.org/show_bug.cgi?id=341143

--- Comment #371 from David Edmundson <k...@davidedmundson.co.uk> ---
Bounty or not, the upstream stance has always been:

"Lets find out why activities do not suffice for your use case and address
that". This somewhat remains.
Three useful comments were made (relative shortcuts, pager and activity bar),
three comments were quickly addressed.

If there are any other actually useful I apologise that they have got lost in
the noise.

----

In terms of activity that /has/ happened, we are well aware that there's a
frustrating and slightly broken overlap between the two.

There have been numerous talks on how to fuse activities and virtual desktops
so the distinction between what's-what is clearer and we don't have the desktop
stuck with this dual cardinality. The most approved suggestion would have
tackled this issue. Windows would be on N VirtualDesktops, VirtualDesktops
would be assigned to an activity. Then we don't have this overlap. Then it
makes perfect sense for the widget configuration to drop down to the virtual
desktop level without causing a feature overlap.

---

In terms of implementation:

Code wise a config option to switch to making things per VD instead of per
activity is relatively trivial. Effectively you can find/replace in
ShellCorona. Keeping that clean (because of the dual cardinality above) is
trickier. Maybe if it was based off a config option as a lazy hack, then maybe
abstracting the index could suffice.

Getting multiple desktopviews so that you also fix the DesktopCube case is
slightly harder, but still pretty easy.
The hardwe part is doing that in a way that you don't ramp up your memory like
crazy. We have the wallpaper in memory, wallpaper in GPU memory, plus front and
back window buffers for the new DesktopView itself. A patch to get in would
have to address that.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to