On Thursday, May 16, 2013 11:01:10 Kevin Ottens wrote: > Only the "emptying" part would be in this magical first activity (otherwise > as you point out it is exactly duplicate). That's the only thing which > makes me uneasy with the idea in its current state: having a magical first > activity which behaves slightly differently than the other ones.
s,slightly,very, all activities should behave identically. otherwise we're going to force the user to build a (relatively) complex mental model of something that is supposed to be supporting their work flow. > But that's > fit my workflow better than having to empty by hand every time. :-) what's wrong with creating a new activity to empty it? you wish to take an activity and then at some point while working on it say "now call this activity $name", yes? sounds like we need a way to: * duplicate a given activity * change a given activity's name easily * create a new blank activity quickly > mistaken currently duplicate deals with the shell state but leaves the > windows alone. yes, ignore the current "add activity" UI a bit as it is a mix between the old presentation of "your desktop is your activity" (which i still think is a very simple, and therefore approachable, way of presenting it) and the new "an activity is an abstract concept, which includes your desktop" duplicating an activity really needs to truly duplicate the *activity*, not just the desktop layout (which is all it currently does). this is PW2 work, and probably requires some support from kactivitymanager -- Aaron J. Seigo
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
