Hi Priss, see below:
On Apr 10, 2007, at 12:29 PM, Priscilla Chung wrote:
*Proposal*
+ Since this is workflow is consistent to Chandler desktop I would
recommend to visit this later post preview.
+ Review this again to identify why it's odd when you unmark an
'all day' item, it become an 'anytime' event and stays in the 'all
day' area.
Sounds good to me.
---
Here are some thoughts I have:
+ Do users really understand the difference by looking at the
lozenge that it's an 'anytime' event?
No, I don't think so. I think we've overloaded anytime-ness / @time-
ness on top of FYI-ness. We should address with a visual syntax
review post-Preview.
+ Would ppl use the 'anytime' event lozenge more if it's made more
apparent to the user that this exists?
Doesn't it start out as anytime?
+ An event can't be both an 'all day' and an 'anytime' event, has
there been thought about changing the 'all day' check box to either
a bullion:
[ ] all day *OR* [ x ] anytime. (Or to save space, use a drop
down list?)
I think we can brainstorm alternatives depending on how people use
the Preview anytime feature.
Terminology:
+ Change the name of the 'all day' area?
I think all-day area is internal. I don't think users are exposed to
this anywhere. Are you proposing we change it internally to make
things less confusing?
+Rename 'anytime' to a more familiar term say 'stickie note',
'scribble pad' (ooh…I like that!) or 'note to self'—because
essentially that is what it is. The lozenge would look different
then other lozenges (and I don't mean a subtle difference in status—
I mean more of a distinct looking lozenge)
I'm not sure that people need to explicitly understand that they're
using the 'anytime' feature. It's more that people should be able to
tell the difference between when they haven't checked the all-day
checkbox and when they have.
It's sort of like how it would be ideal if the way you made @time
events was that you simply omitted the end-time. I think that would
feel pretty natural to people...more so than explicitly designate an
event, an @time event.
But as you said, we should reevaluate based on an analysis of Preview
usage.
+ Perhaps a header can be displayed to identify a different type of
event item, since it is a 'note item'—crossing over to a 'calendar
event item'.
-Priscilla
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
