Summary

This document is an overview of all the functionality proposed for 0.6 that relates to the detail view. The first iteration is simply an expanded feature list to facilitate the design discussions. It will turn into a more detailed spec as 0.6 planning and design progresses.

Next Steps

• Review initial feature list/scope with Bryan Stearns and capture issues - phone meeting scheduled March 7th.
• Update page with detailed design proposals based on initial meeting.
• Schedule subsequent discussion/review for week of March 14th when 0.6 design kicks off.

Proposal

Basic Changes

• Some UI work - improvement in fonts, greyed out hint text. We need to be really specific here.
• Margins all-around. Custom gutters between fields.
• More consistent font faces and font sizes
• Larger font for Title
• Middle-align text in text fields
• Do we want to try and have images for alarms etc rather than text? Yes.
• Triage selector - look at options if adding to mark-up bar is difficult.
• What changes do we want in the markup bar? Custom buttons John mentioned. Reflect event and email status in the stamping buttons.
  • Confirmed, Tentative, FYI
  • In - Unread, In - Read
  • Out - Draft, Out - Queued, Out - Sent, Out - Error
• Field layout changes..ie: vertical to: field? Do we still need this? I think we want to have the field expand as the user types in more addresses. We may also want the To: mary, jane, mark, joe and 51 more people...

Event Detail View

• Improvements to date-time widget based on Mimi's Kibble proposal. [OI^?] Link to Mimi's design proposal.
• Recurrence settings.

Event Invitation Detail View (stamped event and mail)

• Not sure if there is really anything new here.

Email Detail View

• Reply, Reply All, Forward
  • Add a gif for each version of the detail view...what does it look like?
• More polished email addressing [OI^?] Need to define this more specifically.
• Attachments - what is the next phase.
  • Do we have a mechanism to open, save etc?
  • How do we want the current UI changed? MimiYin Clickable links would be a good start.
• Unread, Read, Draft, Queued, Sent - Are we still going to use these?

Task Detail View

• Is there anything new here that isn't covered in the basic category?

Sharing Invitation Detail View

• Need to close on next steps.
• Schedule meeting to discuss widget/ui to represent list of sharees and their statuses (grid-like)
• Change from button to link in received sharing invitation.
• UI for removing a participant from a share.
• Specify readonly or readwrite share.
• Maybe a mechanism to specify what types of items are included in the share - this design needs discussion.

• Caveats
• Some of the more sophisticated mark-up bar widgets for sharing settings depicted below can be reimagined as simple checkboxes and pulldown menus in the detail view
• Specifically: Setting which portions of a collection you want to share can be checkboxes: Mail, Tasks, Events
• Setting ACLs and suspending sharing can be a pulldown menu

• Custom ACLs proposal
• Separate fields for viewers and editors
• Users can add and remove viewers and editors. Newly added sharees look different from sharees that have already been sent invitations.
• Users can mark what portions of the collection they want to share using a widget similar to the stamping buttons.
• Sharing status is displayed in the upper right hand corner. Sharing status is clickable, users click to suspend and resume sharing.
• Sharing_detail_view.png:
  

• Distinguishing new invitees from existing sharees
• Separate fields for existing sharees and new invitees
  • Users can delete sharees from sharees field, but cannot add new sharees
  • Adding names to the invite field (re)activates the Send button
• Single setting for ACL (users set ACL in the upper right hand corner: Not editable, Editable, Suspend sharing)
• Users who do not have edit access to a share can only toggle between Not editable and Suspend sharing
• Sharing portions of the collection works the same as above
• Sharing_detail_alt.png: