[Design][Proposal] Lozenge shape

[Sheila Mooney]

I like this design, particularly the white space around each lozenge  
since it really makes the boundaries of the event stand out. I also  
like the reverse color for the anytime and @time events (indicating  
no duration).

Mimi, I assume that if your event is NOT on more than one calendar,  
the squares do not appear, it's just a plain lozenge?

Sheila

On Apr 24, 2006, at 5:34 PM, Mimi Yin wrote:

> I've pulled together a list of use cases + a final proposal for 0.7  
> event lozenges improvements. Screenshot is below. Thx, Mimi
>
> Use cases that the event lozenge design needs to solve for, in  
> order of frequency of use.
>
> Managing and editing a calendar. Making it easy/clear to grab a  
> lozenge to move it around on the canvas.
> Figuring out when your next meeting/appointment is.
> Figuring out what your next meeting/appointment is.
> Scanning your own calendar to schedule an appt/meeting or figure  
> out a realistic milestone/due date for a task. Which days are  
> packed? Which days are relatively light?
> Scheduling a meeting with other people (by overlaying your calendar  
> with their free/busy or calendar)
> Looking for a particular event on your calendar.
> Final Proposal
>
> What's new
>
> Lozenge outline is white*, which helps to break up consecutive  
> events more effectively in 2 ways:
> Creates a higher contrast divider between event lozenges
> Breaks up the "event status strips", which currently run  
> uninterruped if there are consecutive events
> *The white outline was inspired by some studies Priscilla did:  
> EventLozengeStudies
>
> Event Status Strip is subtler in several ways:
> Default is nothing (for confirmed events)
> Striped tentative strip is narrower
> FYI strip is narrower as well
> Calendar Membership Colors are subtler and replace more and more of  
> the Event Status Strip, up to a limit. As a result, you don't ever  
> get a whole Event Status Strip + Calendar Membership Colors,  
> thereby minimizing the visual noise without losing the meta-data.
> @Time and Anytime events are more distinct from events with duration
> @Time and Anytime events are distinct from events with duration in  
> a semantically meaningful way (they are "less saturated" because  
> they don't actually take up time)
> Selected calendar lozenges are more distinct from activated, but  
> not selected calendars:
> Lozenge fill color is more saturated
> Text is white on lozenges belonging to the selected calendar
> We may also want to consider exploring some alternatives for making  
> the Event title more prominent than the Start-time on the lozenge,  
> as per Priscilla's mock-ups: EventLozengeStudies
>
> <dotseven_lozenges_5.png>
>
> ===
>
> What we've done:
>
> 1. Mimi compiled a list of all the different pieces of meta-data  
> that may need to go on the event lozenges and put forth 3 proposals  
> which took into dogfood feedback:
> http://wiki.osafoundation.org/bin/view/Journal/ 
> EventLozengeImprovements
>
> 2. Mimi did a 4th iteration based on feedback from the list:
> http://wiki.osafoundation.org/bin/view/Journal/ 
> EventLozengeImprovements#FourthIteration
>
> 3. Priscilla did a pass at the lozenges: http:// 
> wiki.osafoundation.org/bin/view/Journal/EventLozengeStudies
>
> <dotseven_lozenges_5.png>
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "Design" mailing list
> http://lists.osafoundation.org/mailman/listinfo/design

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osafoundation.org/pipermail/design/attachments/20060425/a1ce2b13/attachment.html