23

I like the idea of tying sessions to activities as it definitely broadens the scope of activities to more than just virtual desktops for plasmoids but also ties a set of applications to the activity.

Perhaps the saving of activities should be handled by a configurable policy with a couple of different the options: Save changes immediately/on logout/activity close - the saved activity is kept up-to-date as applications and plasmoids are added and removed, requires new activities to be added manually and named when added (or you can save the activity as a new activity and make changes from there); Save changes explicitly - changed activities may be saved overwriting the currently saved version or may be saved as a new activity.

I would also propose that activities be loaded on-demand: only start the start-up activity (a specific default activity, or the last used activity as determined by policy set by user), then load other activities when they are requested. The benefits here are that the load for initially starting up your desktop and total memory usage is reduced (assuming users generally don't switch to all activities in a given login session). The downside would be a small performance hit when switching to other activities for the first time as that activity gets loaded.

I think what Madman is talking about is having activity "templates" that you could use. Which I think has already been discussed. Anyways, that would be a feature for a later date and time, lets get activities working first lol.

@ivan: will activity's be completely replacing sessions and virtual desktops? To the point where those are removed in their current form? B/c to me it seems like its an expansion of those same concepts.

And most of the configuration for activities could easily be done the same way as virtual desktops I would think.

airdrik wrote:I like the idea of tying sessions to activities as it definitely broadens the scope of activities to more than just virtual desktops for plasmoids but also ties a set of applications to the activity.

Perhaps the saving of activities should be handled by a configurable policy with a couple of different the options: Save changes immediately/on logout/activity close - the saved activity is kept up-to-date as applications and plasmoids are added and removed, requires new activities to be added manually and named when added (or you can save the activity as a new activity and make changes from there); Save changes explicitly - changed activities may be saved overwriting the currently saved version or may be saved as a new activity.

I would also propose that activities be loaded on-demand: only start the start-up activity (a specific default activity, or the last used activity as determined by policy set by user), then load other activities when they are requested. The benefits here are that the load for initially starting up your desktop and total memory usage is reduced (assuming users generally don't switch to all activities in a given login session). The downside would be a small performance hit when switching to other activities for the first time as that activity gets loaded.

I completely agree

Nothing UI-wise is yet decided - we'll be discussing that in lengths during Tokamak4 (started today).