Notes: Visuals For Scooby And Chandler

These are notes about how the visuals in Scooby may match the visuals Chandler, but only where it makes sense to be consistent. Primarly based on giving a co-hesive front for the OSAF ecosystem. Currently there has been visual design explorations primarily for event lozenges based on Mimi's email thread on the design list. Please review notes below.

Lozenge Visuals that are not in Chandler

• • Start time bar
  • End time @ the bottom feedback
  • Transparency

Visuals that are in Chandler

• Rounded on all four corners
• Consistent color scheme
• Consistent visual syntax events status (anytime, @time, FYI)

Calendar canvas

• Timeline
  • Preferences to timeline view
  • Look of the time line (visual indicator @ noon)
• Work day shading

Layout

• More space in Chandler, less space in Scooby

What's driving the visuals?

• Branding
• Functionality
• Browser has a toolbar/side bar chrome/wrapper

Dog Food-able release for Scooby

• Read only
• Background/auto sync with chandler (ie. web email applications)
• Recurring events
• Data availability

1.0 for Scooby

• Subscribe to calendar (Chandler, iCal, RSS feeds) button to Scooby
• Editable
• From e-mail--> one click to single item view
• Need to understand Chandler data model
  • Scooby understanding stamping
  • user define attributes
  • meta data from e*mail/communication

Question

• Does Scooby need to support more then Calendar for 1.0? In order to support the ecosystem?
  • If no, here's an example: If a Chandler user publishes a calendar to a drive by user. The drive by user will only need to view events, not tasks or any other PIM functions in Chandler. Thus this is still an example of a use case within the ecosystem.
  • If yes, then we need to take into account features such as table view tasks --> will give search capabilities.
    • Though will this be an expensive feature to build given the timeline of product release?

-- PriscillaChung - 19 May 2006