On Dec 12, 2006, at 2:45 PM, Brian Moseley wrote:
On 12/12/06, Ted Leung <[EMAIL PROTECTED]> wrote:
The people that it's tough for is
*us*, the designers and the engineers, because we're going to have to
spend time time to think about these sorts of problems and find ways
to ease the pain. It means we might have to try/build 3 or 4 or 10
designs in order to get it right. And if that's what it takes,
that's what we're going to do.
i don't define "get it right" as "treat users as if they are stupid",
but that's what i feel sometimes in these design discussions, even
though i know that's not what mimi or priscilla is actually thinking.
Ok, fair enough -- but the "tough" at the beginning of your paragraph
didn't help in communicating what you actually think.
i'm all for a tool that makes it easy for the user to do his shared
calendaring stuff. but i'm not for obscuring or flat out hiding
things. when apple does this it makes me want to scream. there's got
to be some kind of balance between the apple and microsoft extremes
that lets users take a little control over how they use their own
software. i'm not asking for every user to understand or care about
competing calendaring standards. i just want the "power user" (which
is a term that i think marginalizes the people who are most likely to
use our software in the next year) to not be frustrated by our
over-catering to the "simple user".
So what did you think about my proposal for a menu that controls what
url gets displayed? The entries in the menu might look like this:
Chandler
iCal 2.x
Sunbird
Evolution
-----------
Other....
DAV - (is there something more descriptive here)
Atom
Morse Code (is there something more descriptive here)
Webcal
Download in iCalendar format
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
