psifidotos
commented
11 years ago This is ready and works fantastic.... :) except of "--add new Workareas to those Activities which were in maximum size before adding a new Desktop"
it would create inconsistences....
in development branch the code... :)
Well, I hope the title is not confusing :)...
I want to address the following situation:
Differences To Default KDE workflow Workareas use Virtual Desktops, in order to be consistent between them, Virtual Desktops are always that big as the maximum Workareas present from Activities. NOTICE: You can not add a Virtual Desktop when Workareas are running. You can add the Workarea needed and Virtual Desktops will be updated.
Well this does not work as good as I would like... It can create much confuse to new users and I definitely do not want that. The target should be the following, when a new user achieves to install the plasmoid or the kwin script then that must be the most difficult thing for him. What I propose about adding/removing workareas etc.: [b]Adding a Workarea from Workflow Components: --this is easy, update the desktops number in Plasma according to Workareas (this the current behavior)
Removing a Workarea from Workflow Components: --this is also easy, update the desktops number in Plasma according to Workareas (this the current behavior)
Adding a Desktop from outside the Workflow Components(e.g. the default pager): --add new Workareas to those Activities which were in maximum size before adding a new Desktop
Removing a Desktop from outside the Workflow Components(e.g. the default pager): --hide(but not delete) all Workareas which do not correspond to the new desktops length. (that gives the user the possibility to restore easily any workareas hidden by mistake)[/b]
The above I would call Phase 01...
In Phase 02 can be observed new UI decisions for example give the user the feature to show/hide all desktops that are not used from Workareas. This has been proposed from Michael in one of the closed issues which cant recall right now...
What do you think?