Alpha 4 Detail View

I've tried to pull together all Alpha 4 detail view feature work in 1 place. This page is compiled of feature work described in the following:

• ModalAddressingFields
• ExpandoDateTimeFields
• StampingStoryboards
• http://svn.osafoundation.org/docs/trunk/docs/specs/rel0_7/Stamping-0.7.html
• http://svn.osafoundation.org/docs/trunk/docs/specs/rel0_7/Dashboard-0.7.html

Elements

• Mark-up bar
  • Triage status button
  • Stamping buttons: Address this, Add to task list, Add to calendar
  • Privacy lock
  • Read-only status icon
• Expando Addressing fields
  • From
  • To
  • CC
  • BCC
  • Send via [Select account from pulldown]
  • Edited by [Select account from pulldown]
  • Non-editable metadata
    • Sent by 'Name' on 'Date'
    • Edited by 'Name' on 'Date'
    • Updated by 'Name' on 'Date'
    • Created by 'Name' on 'Date' (only for items not created by you)
• Title
• Location
• Expando Date/time fields
  • All-day checkbox
  • Start date
  • Start time
  • End date
  • End time
  • Timezone
  • Event status
  • Recurrence
  • Recurrence end date
  • Alarm
    • Custom ticker date alarm option
• Notes

Special requests

• Addressing fields can store any alpha-numeric string (in other words, doesn't have to be a properly formatted email addresses)
  • If an user hits Send on a message that has non-email addresses in the addressing fields, we should throw up a dialog warning them that: This message will not be sent to the following people: gobbledy-gook1, gobbledy-gook2. [Fix email addresses] [Continue]

• • If there are no properly formatted email addresses and users try to hit Send, then we should throw up a dialog that says: This message cannot be sent because you have not entered any email addresses. [Okay]

• Date/time fields can store any alpha-numeric string and/or nothing
• This is true of the start/end date/times, the recurrence end date field AND the custom tickler date field

Post Alpha 4 (not depicted here)

• Labels

Nice-to-haves

• Pop-up fields (to be able to view and edit fields when the text exceeds 1 line) (see below)
  • I'm assuming this is hard...so for now, let's do a text field that is just big enough to accommodate a vertical scrollbar (2 lines of text?)
• Custom hint text for the addressing field (depending on Kind)
  • If the item is a Task:
    • From: Enter task requestor
    • To: Enter task requestee
  • If the item is an Event:
    • From: Enter event organizer
    • To: Enter event participants
  • If the item is just a Message
    • From: Enter sender
    • To: Enter recipients

Visual guidelines

• Font size: Medium (11 point on the Mac)
• Default Font color: Black #000000
• Empty values are greyed out (50% grey)
  • Hint text in addressing fields
  • Location
  • Hint text in date/time fields
  • None in Alarm pulldown
  • Custom in the Alarm pulldown if no custom date has been specified yet (see comps below)
• Title field is never allowed to be empty. Always says at least: New Task / Event / Message or Item
  • Task-ness overrides all other kinds
  • Event-ness overrides Email-ness
  • Email-ness overrides Note-ness
  • If no stamps are applied, it's just an Item
• Title field is Extra-Large font size: 15 point and Bold.

Alignment

• Text in the detail view should not go beyond the left-margin set by the text in the Notes field.
• Attribute labels are right-aligned
• Attribute values are left aligned
• Fields without separate Attribute labels are left-aligned
  • Uneditable metadata
  • Title
  • Location

Comps

Caveat The addressing fields and date/time fields would never be in edit mode at the same time.

Alpha4_DetailView_View.png	Alpha4_DetailView_Edit.png
Alpha4_DetailView_ViewAgain.png	Alpha4_DetailView_Guides.png

-- MimiYin - 14 Jul 2006