connecting/disconnecting from activities

[Aaron J. Seigo]

On Friday, July 29, 2011 12:01:55 Arjen Hiemstra wrote:
> Put the "Current Activity" in the top menu, and
> keep the Activities entry that changes to the submenu. This allows you both
> quick access to the (imo) most relevant entry, and also allows you fine
> grained control over the associations. 

that's possible, and something i even considered. my concerns are:

* it means having two entries for the same thing, which means understanding 
why there are two and which one you want

* this menu will fill up with other items that are likely to also offer 
options, e.g. "Event". it would be nice if there was a consistent workflow 
amongst them all and if we can keep the list as compact as possible (e.g. one 
entry per connection type)

the benefit of what you suggest is that one tap is avoided when connecting to 
the current activity. the assumption being tha the current activity is the one 
people will most often choose (which may be an accurage assumption, though we 
don't know yet).

imho the added entries and use case inconsistency, which would likely lead to 
higher cognitive load, is not worth it.

> Possibly they even could be merged
> into a single entry that behaves slightly different on short/long tap or
> using some kind of "More" indicator.

every time long tap is considered, $DEITY kills a kitten. ;P

-- 
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Qt Development Frameworks
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/active/attachments/20110729/ef2ffdec/attachment.sig