http://wiki.osafoundation.org/bin/view/Journal/EventLozengeImprovements
So of course, just as I replied to matt saying that the @time and
anytime lozenges wouldn't change very much, Mitch's email prompted me
to have another go at the event lozenges in the calendar, which
prompted me to draw a laundry list of all the pieces of meta-data
that should/could go on the event lozenge...which turned out to be
rather long.
Note: Apparently it is hard to draw the solid banner at the top of
the event lozenge, which is why we didn't consider this design for
0.6 (a la iCal) (Alec, correct me if I'm wrong)
Mimi :o)
On Apr 5, 2006, at 9:59 AM, Mitchell Kapor wrote:
I'm now dogfooding 0.6.1. I've put away iCal, at least for a
week. So far, so good, as they say. My assistant, Esther Sun,
keeps my calendar, so my primary use case is frequently consulting
it to see what I have to do next, what the current day is like , or
how busy is a specified interval in the future. I have a fairly
full calendar and it is not unusual to have 4 or 5 consecutive
appointments of 30 or 60 minutes duration each.
The visual separation between multiple consecutive events is not up
to par. The problem is that it's hard to tell where one event ends
and the next begins. The shape of each event is rectangular on the
left side and nearly so on the right, with only a very small curved
cut-out at the top and bottom edge. I think it would really help
if the event "lozenge" was actually more lozenge-shaped so that a
series of consecutive events would read more as a set of oval
lozenges stacked on top of one another rather than a stack of
slightly defective legos._ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
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
