r5 - 16 Aug 2005 - 11:59:31 - MimiYinYou are here: OSAF >  Projects Web  >  UIDesignArchive? > DesignReview20040831

Design Review: Session 1

Goals

  • Kibble strategy
  • Provide roadmap for scope of design review series
  • Describe what we will try to cover today
  • Overview of basic Chandler concepts
  • Overview of basic Chandler UI components
  • Overview of design process. See DesignProcess
  • Get feedback on user mental model and workflow
  • Discuss interaction issues
  • Defer any detailed discussions about visual design
  • Evaluation and Next steps

Roadmap

We're taking a workflow-based approach derived from David Allen's Getting Things Done

  • Collect and Create
  • Process
  • Orgcess
  • Organize
  • Retrieve
  • Review
  • Do

Today, we're going to cover Process, Orgcess and some aspects of Organize. We feel that these are the central use cases and main areas of innovation for Chandler as an information management and organization tool.

Things we're specifically not covering:

  • Create
  • Universal text entry box

  • Advanced organizing
  • Rule builder
  • Collections Manager
  • Sharing

  • Retrieve and Review
  • Search
  • Browser (not even in Kibble)

  • Doing

  • Application areas
  • Email
  • Calendar
  • Contacts Management (not in Kibble)
  • IM (not in Kibble)

  • Horizontal utilities
  • Undo framework
  • Chrome other than sidebar e.g. toolbar, tabbed views
  • Printing
  • User alerts, status, notifications, logs & diagnostics
  • Import / Export / Syncing
  • Preferences
  • Installer and Updates
  • Help

Basic Chandler concepts

  • A content item is a personal information item relevant to the user (ie. a message, a task, a calendar event, a note). Content items are represented as a single row in the summary table view or as a physical block of time in the calendar view. Content items do not include repository items such as collections, blocks and views.
  • A collection or named collection is a group of content items. Collections are persistent and have user-defined names. Collections can have a user-defined rules and a list of inclusions and exclusions. Collections live in the sidebar and also in a Collections manager. Users can also see the collections a content item is a member of in the See also sections of the content item's detail view.
  • Clusters are light-weight collections that open in-place in the summary table view. Clusters will display content items in-place even if those items do not belong to the currently selected collection. Clusters are most similar to Message threads in email clients today. Content items can belong to multiple clusters. Clusters can also be accessed from the See also section of a content item's detail view.
  • Ephemeral collections are temporary, unnamed collections of items (ie. search results). Users can save ephemeral collections and turn them into first-class named collections.

  • Interaction abbreviations
  • DnD: Drag and drop
  • DnH: Drag and hover

Basic Chandler UI components

  • Main toolbar
  • Search bar
  • Sidebar with Kind filter and mini-calendar browser
  • Main content area
    • Summary view
    • Detail view

[LOOK AT LATEST BUILD]

  • What we will cover today
  • Sidebar and Kind filter
  • Dashboard collection and Summary table view
  • Stamping and Detail view
  • Chandler_landscape.gif:

Design pages

-- MimiYin - 27 Aug 2004

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r5 < r4 < r3 < r2 < r1 | More topic actions
 
Open Source Applications Foundation
Except where otherwise noted, this site and its content are licensed by OSAF under an Creative Commons License, Attribution Only 3.0.
See list of page contributors for attributions.