Preview Cosmo Styleguide Review Apr 26, 2007

Agenda http://lists.osafoundation.org/pipermail/design/2007-April/007013.html

Attendees

• PriscillaChung
• MatthewEernisse
• TravisVachon
• TedLeung
• MimiYin

Meeting goals

1. Understand what is this possible for Preview?
2. FYI: Where is PPD on this issue?
3. Gathering input on how to better communicate styleguide requirements.

Button Styles

• State buttons versus Action buttons
• Experiment with Stamping buttons
• Email this event: Unclear whether we have In-band versus Out-of-band emailing
  • Add a tooltip? How would we word it?
  • Add an alert dialog
  • In-band emailing is out for Preview

Keyboard support

• No tabbing across the UI
• Tabbing within the Detail View
• Support DELETE button when focus is on
• Enter will work if you're editing single-line fields, not the Notes field
• mde: Come up with a list for where keyboard works and doesn't work
• There's a bunch of weirdness: If you select an event lozenge and hit [backspace], you go back in the browser

• Can we have visual feedback for where you have keyboard focus within the 3-pane layout? Not for Preview.

Go to Date

• If you enter a Go to date from the Dashboard, Chandler Hub takes you to the calendar

Mini-cal

• Click on the mini-calendar will take you to the Calendar view

Quick item entry

• Creates new note
• Text is entered into the Title field
• Item is added to the top of the Dashboard
• Item is given a triage status of NOW

Form elements

• Trouble with flat outlines on Safari
• Change style when it has focus: Not in Safari
• mde: Might not be able to tab to a custom pulldown
• Open issue: Do we still want custom pulldown if you can't tab to it

Detail View

• Make the byline field a form field when you edit the item
• Byline does not need to be in the email
• Okay with grey text to display the alarm
• Open Issue: What is our capitalization scheme?
  • Title Case, where all important words are capitalized?
  • Sentence case, where only the first word is capitalized?
  • lowercase, used in situations where there are a lot fields?

Dashboard

• Make items display on 2 rows on a case by case basis
• If there's nothing to display in a row, get rid of the extra space
• Read versus Unread: Bold versus Not-Bold: Open Issue Can we detect Read/Unread status?
• Can we do Candy stripes? Dividers? Yes to both.

Pagination

• We will display 25 items per page and see how that goes.
• Should the pagination UI be consistent with the Admin UI? Doesn't need to be, since the user populations are very different.
• Proposed design: << [#] of Total# >>
• UI Issue Because we are not supporting sections for the Hub Dashboard, it will be hard to find the Later versus Done sections.

Resizing

• We will calculate the width of the Dashbord columns depending on the user's browser window size
• Users can resize the entire UI, but not the individual columns separately
• UI Issue Remove and Save buttons are hidden because they are too far down

-- MimiYin - 26 Apr 2007