The notion of contacts being just as stampable as any other item appeals to me conceptually, but the use cases aren't particularly convincing to me. Personally, it seems to me that the most useful workflows would involve easy creation of links from events, tasks, and messages to contacts, and easy navigation/overview of back-references from a contact to all items that link to it. And correct me if I'm wrong: the support for this kind of functionality exists in the model as far repository is concerned, but it's less obvious how it would be implemented in the UI.
Conceptually at least, it would be almost like each contact were a collection in the sidebar; selecting it would show items referencing it in the summary view -- as usual, further filtered by the app area (finally a good use for All!). But a contact is also more than a collection, because it would need to be displayable in the detail view so that the name and other info can be edited, not to mention that showing contacts as top-level collections would quickly overcrowd the sidebar. Anyways, just some thoughts on what would be the big wins in my view. Davor _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
