Meeting to discuss scope of detail view work for 0.7 (at a design perspective)

Attendees

• In person: Bryan, Mimi, Sheila, Priscilla
• On phone: Philippe

Notes

Agenda

• Showing/hiding fields in the detail view (Addressing fields and Date/time fields)
• Scrolling the entire detail view
• Label field for both tags and user-defined attributes
• Notifications about conflicts due to sharing or item updates
• Next actions

Detail view update

• What work we have done so far
  • added cc, bcc fields
  • from address - outgoing message - from is a popup that list your outgoing email address from your accounts
  • to address - now an attribute editor - completion works on it and with individual addresses in it

Label field discussion

• Appears in field will now become a user-editable label field
• Label field will contain tags (ie: bryan, cosmo, school) and
• User-defined attributes that get created on the fly by the user (ie: School: P.S. 187)
• User-defined attributes are specific to the item (not to the Kind)
• Tags, User-defined attributes and OOTB attributes can be collections in the sidebar

• Most of the tough architecture issues around user-defined attributes will be addressed as part of the domain model project for 0.7 - owned by Ted

• Interaction affordances

• We need to iterate on what affordances we provide to help users understand the relationship between attributes in the detail view and collections in the sidebar. ie:
  • Add an asterick at the end of attribute values that have been added to the sidebar as a collection
• Context menu support for:
  • Add/Remove an attribute value to the sidebar as a collection
  • Search on an attribute value
  • Assign a different attribute to the attribute value (ie. Not Author: Bryan, but Co-author: Bryan)
  • Edit name of attribute

• Autocompletion: we will do the simplest auto-completion possible, meaning:
  • If user types an attribute value that is assigned to multiple attributes, we will NOT try to guess which attribute the user intends.
  • We will not be able to auto-match attributes added to the label field with existing OOTB attributes (ie. user labels an item, From: Bryan, this label will not be resolved with the OOTB "From" attribute.

• What needs to happen in the sidebar
• Create a new collection in the sidebar
• Name the collection: Research dentists
  • If you have already labeled stuff Research dentists, then the collection needs to pull together all those items
  • All subsequent items added to the collection are automatically labeled with the generic tag: Research dentists OR
• Name the collection: Project: Research dentists
  • If you have already labeled stuff Project: Research dentists, then the collection needs to pull together all those items
  • All subsequent items added to the collection are automatically labeled with the user-defined attribute, Project: Research dentists OR

Conflict notifications

• We did a review of how updates will work and the limitations in the UI
• We still don't know what will happen when we make changes in Chandler (that are not yet committed) and we have a conflict
• There will be some UI implications but we still need to explore proposals to either stage this or have a simple solution for 0.7

Scrolling

• Bryan will try and do scrolling for the whole detail view
• If this doesn't work, we will opt for scrolling individual fields

ExpandoDateTimeFields proposal

• Looks like at first glance Mimi's expando proposal should be ok
• http://wiki.osafoundation.org/bin/view/Journal/ExpandoDateTimeFields

ExpandoAddressingFields proposal

• Reviewed Mimi's proposal
• Bryan came up with a better one, which would basically treat the Addressing fields like the Expando Date/Time fields
• See new proposal here: ModalAddressingFields

Next actions

• Get Bryan involved in the relevant domain model discusions with Ted and others
• Mimi drafting a modified proposal for expanding/collapsing sections to circulate: see ModalAddressingFields
• Sheila will work on outline of a spec - at a minimum requirements, feature list and assumptions
• Bryan will read and respond to Morgen's thread on the design list regarding auto-sync and conflicts
• Need a follow up discussion to talk about conflicts and the UI