Duh. That's the reason why we didn't have 'My calendar' originally. I
think part of the reason was that it's not only a calendar, but a
collection. From a user's perspective, the casual collaborator may
not be aware of the term 'collection'.
+ Would it be understood by users if the default label said 'Brian's
collection'?
+ Do we introduce this term to users who may not have a clue about
Chandler and have them learn what a 'collection' means?
Maybe it's not a big deal, and users won't think twice about the
term, (as I'm doing) rename the collection to whatever they want anyway.
I realize the 'collection' term is used on the desktop as one of the
menu items, but once again if the target users for the web UI are not
familiar with Chandler…is this a term we want users to have to learn
since it's not apparent on the surface such as 'calendar'?
To keep things simple, should we just keep the term 'Chandler' for
preview? Post preview, maybe it's about making the personalization
leap to 'Brian's Chandler'. ;)
-Priscilla
On May 10, 2007, at 10:57 AM, Matthew Eernisse wrote:
Now that we're doing some minimal dashboard stuff in the Web UI,
might we not consider "<username>'s collection"? (As opposed to
using the word 'calendar.')
The UI code now supports parametric replacement in the localized
strings (we can move stuff around to support different word order
and grammar), so I don't even think localization would be a problem.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
