Overview

This page details the desired behavior of the sidebar and application bar filters for 0.5. The kind filters have been moved to the toolbar and renamed the application bar giving the user the more prominent view of the application areas and quick navigation to frequently used views ie: my calendar. By intersecting the selection in the sidebar and the application bar selection the user obtains a view for this particular slice.

Assumptions

• No reordering of sidebar items.
• Sidebar items appear in the same order for every selection in the Application Bar.
  • All , In, Out, followed by user defined collections in alphabetical order.
• You cannot multi-select items in the Application Bar.
• You cannot multi-select collections in the sidebar.
• There is no divider in the sidebar between OOTB collections (All, In, Out) and any user defined collections.

Detailed Workflows and Use Cases

Use Case #1: New user runs Chandler : OOTB view

Success Criteria

• a. By default the application bar has the All bar item and the All sidebar collection selected
• b. The List view is displayed in summary view.
• c. Selecting the In collection displays the list of all received items.
• d. Selecting the Out collection displays the list of all sent items.

Use Case #2: Select mail application

Success Criteria

• a. Clicking on the mail application selects the All sidebar collection by default .
• b. The List view is displayed in summary view by default.
• c. Selecting the In collection displays the list of all received mails.
• d. Selecting the Out collection displays the list of all sent mails.

Use Case #3: Select the calendar application

Success Criteria

• a. Clicking on the events application selects the sidebar collection "All my events" by default.
• b. The Week view for "today" is displayed in the summary view.
• c. Selecting the In and Out collections in the sidebar while in the Events app changes to the summary table view list display.
• d. Selecting the In collection displays the list of all emails that we have received and stamped as events.
• e. Selecting the Out collection displays the list of all events that we have stamped as emails and sent out.

Use Case #4: Select the task application

Success Criteria

• a. Clicking on the tasks application selects the sidebar collection "All my tasks" by default.
• b. The List view is displayed in the summary view.
• c. Selecting the In collection displays the list of all mails that we have received and stamped as tasks.
• d. Selecting the Out collection displays the list of all tasks that we have stamped as emails and sent out.

Use Case #5: Layouts, selection and persistence.

• a. Summary view columns, ordering (ie: message history column before who column) and width are persistent per app bar selection.
  • i. We select "All" app and "All my items" collection and change the column widths in the summary view. If we click any other collection in the sidebar, the column widths are persisted. Clicking on the Mail app changes the column widths to those used the last time we were in the Mail app.
• b. The sort order in the summary view (sort column) is persistent per app bar selection and sidebar selection.
• c. The sidebar collection selected is persistent per app bar item. If we select "All" and "Trash" then click to "Mail", "All my mail", if we go back to "All" the "Trash" collection will be selected.
• d. The summary view table width is persistent with the app bar selection.
• e. The width of the app window is persistent with the instance of Chandler.
• f. Item selected and scrollbar positioning - 1 setting per instance of a collection per Application bar selection (ie. The same collection is loaded into 2 different tabs. Each instance of the collection maintains it's own selection.) Since this is hard to do, fallback might be, 1 setting per Collection per Application bar selection.
• g. For the calendar app, the date range selected persists across all the calendar collections in the the sidebar.

Use Case #6: Create a new Item

Success Criteria

• a. If the user is in the Calendar app, they can create an item using in-place editing and are not forced to the "All" mode. For 0.5 only the calendar will have in-place editing.
• b. User stamps a note as a mail then goes to Mail app "All my mail". The note is there, stamped as mail and note. (same behavior for stamping other kinds)
• d. If the user has an Event which is also stamped as a Mail, unstamping it as a Mail will remove it from the Mail app for this collection.

Use Case #8: Create a user defined collection

Success Criteria

• a. Create a new user defined collection which will appear in the sidebar in alphabetical order with the other user defined collections.
  • i. Select collection menu item New Collection.
• b. By default, user defined collections do not have an icon to the left of the text.

Use Case #9: Change the name of a sidebar collection

Success Criteria

• a. Changing the name of a sidebar collection changes the name across all apps.
• b. The user can change the name of a sidebar collection in any app (regardless of whether or not there are items in the collection for that app).

Use Case #10: Drag and drop items into sidebar collections

Success Criteria

• a. Dragging and dropping items into a kind specific tab automatically stamps them as this kind.

Use Case #11: Row in the sidebar collection

Success Criteria

At any time, one row in the sidebar could display any of the following properties.

• Name
• Sharing status
• Icon - only for OOTB collections All, In, Out, Trash
• Selection - which item is selected
• Message counts (not in 0.5)

Assumptions and Details for 0.5:

• 1) My sidebar shows every category of remote origin items OR if "null" category appears -> collapse to 1 per user.
• 2) No access control GUI -> invitations can go to anyone with no ALL implications
• 3) No merging of categories
• 4) No multi-select of categories
• 5) Stamped items might be shared twice ie: a "work" event + task shows up in both work events and work tasks on server - also items in 2 categories uploaded twice.
• 6) Can only add appropriate items (by kind) to a share of remote origin ->worst case they are deleted when you sync ->best case, prevent user from adding
• 7) Sharee can't see both All and category from same server.
• 8) drag item into category it's assigned that category -. if dragged to stuff it has not category.
• 9) Can't edit share name in sidebar
• 10) deletion on (if we get to it would happen silently)
• 11) For 0.5 all items in a share are added to my all collection.

• DesignEngFilteredShares20041116

Deferred Features from 0.5

• Icons next to the OOTB collections in the sidebar.
• Text for All Collection depending on app bar item selected
  • All my items
  • All my tasks
  • All my events
  • All my mail
• Text above appears in summary view tab.
• The specific icon appears to the left of the "All..." collection name - depending on app bar filter.

• Item Creation
  • a. When the user creates a new item from the New button or New menu item, Chandler jumps to the "All" app and "All my items" collection by either.
    • i. Selecting the All tab if it is already open.
    • ii. Opening up a new tab and loading it with the "All my items" collection in the "All" app.
  • b. If the user is in the Calendar app, they can create an item using in-place editing and are not forced to the "All" mode. For 0.5 only the calendar will have in-place editing.
  • c. User stamps a note as a mail then goes to Mail app "All my mail". The note is there, stamped as mail and note. (same behavior for stamping other kinds)
  • d. If the user has an Event which is also stamped as a Mail, unstamping it as a Mail will remove it from the Mail app for this collection.

• Collection Creation
  • • Double-click on white space in the sidebar (is this in 0.5?).
    • By default the collection name is greyed out if there are not items in it. This is the same across all Apps.
    • If the user clicks on the Mail app and it has not items, something in the summary view is display indicting "no items of this type".
    • Add a mail item to the collection and the name in the sidebar will not be greyed out when we click on the Mail app or the All app.

• Dragging and dropping items into a kind specific tab automatically stamps them as this kind.

Use Case #12: Sharing intersection of sidebar and app bar selection (deferred from 0.5 - sharing a collection shares the whole row)

Success Criteria

• a. User A selects a user-defined collection Home and clicks on the Events app to share with User B.
• b. User B receives the invite and accepts the share. A new collection "User B Home" appears in their sidebar.
• c. Both User A and User B will see the sharing icon next to this collection when they are in the Events app.
• d. When the User A or B is in the All app, the sharing icon is visible but greyed out, meaning partial share.
• e. If they select the Mail application, the collection in the sidebar will have no sharing icon.
• f. User B can see items for that collection in the Mail app and Task app only if they are shared events that have been stamped as mail or tasks.
• g. If a shared event is unstamped as a mail, it disappears from the Mail app view.
• h. User B cannot add items into that collection that are not of the Event kind ie: drag and drop a task into the Task app. They can add Events into the All app or the Events app and stamp those as mails or tasks.
• i. User A can add any items to that share that are NOT Events but those will not be uploaded to the server and shared with User B.
• j. User A decides to share the Tasks associated with the Home collection (select Home and Tasks app).
• k. User A will see the greyed share icon in the All app with the Home collection selected. The sharing icon will appear in the sidebar when the Task or Events apps are selected
• l. Upon accepting the invitation User B will also now see the sharing icon when they select "User A Home" and the Tasks app. The new share is not put on a separate line in the sidebar, behind the scenes it firgures out that we have shared 2 different slices of the same collection.
• m. User B can add items to the Task share as well as the Events share but NOT the mail share (unless the tasks or events were stamped as a mail, then they appear automatically).
• n. User B cannot change the name of the shared collection.
• o. If User A had shared the All Home rather than the Events then shared Tasks, User B would accept the invitation for the task share but see no visible difference since they already have the tasks by sharing All.
• p. [OI^?] What happens if the user does case "o" in reverse?

Issues List

• A filter share solution has not been found for 0.5.

Status

Notes

-- SheilaMooney - 05 Nov 2004