On Friday, March 30, 2012 11:51:02 Thomas Pfeiffer wrote: > since it has become relevant to the discussion about the "Edit Activities" > dialog, I will now present an idea that Fania, Thorsten Prante from > Zeitgeist and me had at the last PA sprint.
this sounds cool. will it get used? in this manner? would a more common use case be that when "Anne receives an email asking her to prepare a presentation for a meeting on very short notice." she wants to pull together all information related to that topic that already exists? or an activity that reflects / is based on / is the activity related to that task of the person who sent it to her? i don't have enough usage data to know. i doubt any of us do because this kind of data will only come through people using it. right now it is speculative: it could be a feature lots of people use fairly frequently, one that is used by a few people lots, or used by lots of people rarely. or by "no one". my concern is that implementing this kind of feature (including Ivan's expansion of it into activity clone-and-reduce) increases the UI load for all users of activities. if it ends up not being a common use case, we'll have degraded the experience. honestly: i really do not think we should be doing much more work on the shell right now. it will likely only make it more complex before we have a strong user base that has learned what we have already (which already comes with some learning curve, but an approachable one right now), and we have tons of things that actually do need doing elsewhere in the user experience. example: i have received _numerous_ requests for shared and/or synchronized activities, based on actual not-made-up use cases. implementing that would be guaranteed to grow out user base. it may not sound as sexy, but it's completely practical and desired and could probably be done without impacting the shell itself. another example: we have recently received a possible entry for ebook reader, and it needs UI love. i already gave the author some feedback and they are currently setting up a repository on git.kde.org for it (previously was hosted elsewhere). -- Aaron J. Seigo
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Active mailing list [email protected] https://mail.kde.org/mailman/listinfo/active
