[Design] [Sum] Jun 5-11

[Sheila Mooney]

New Design Discussions:

Mimi forwarded an email from Brian K that raised issues around how we  
use In and Out in the context of shared email. Mimi explores several  
possibilities but presented the discussion to a wider audience on the  
list.
http://lists.osafoundation.org/pipermail/design/2006-June/004811.html

Sheila sent out an updated version of the sharing spec with a few  
changes identified for Alpha4. Mimi replied with a proposal for not  
sharing only a portion of a collection if we publish and we are not  
in the All app area. Based on some user feedback and the fact that  
users will now be in other app areas ie: task, email, all she  
questioned whether or not we wanted to change the assumptions we made  
for 0.6. Users could change this via a manage share dialog.
http://lists.osafoundation.org/pipermail/design/2006-June/004814.html

Sheila sent out the first draft of the 0.7 sidebar spec to the list.
http://lists.osafoundation.org/pipermail/design/2006-June/004809.html

Sheila sent out a new version of the Mini Calendar and Preview area  
spec. Based on user feedback, there are a number of small changes on  
the table for Alpha4.
http://lists.osafoundation.org/pipermail/design/2006-June/004815.html

Sheila sent out a draft of the Alpha4 Dashboard spec for review.
http://lists.osafoundation.org/pipermail/design/2006-June/004834.html

Mimi sent out a proposal for rationalizing the overlay behavior in  
the sidebar and addressing a number of open issues that have been  
floating around. Since 0.6 was focussed on the calendar, we didn't  
talk about how overlays would work in the other areas of the  
application or how to make them usable in the table view. She put  
together a detailed proposal to initiate some discussions of how we  
might want to consider handling this for 1.0...
+ how users will use overlays for user-defined and out of the box  
collections
+ what will happen to the overlays as the user changes app areas or  
tries to overlay user-defined and ootb collections.

In summary, Mimi believes the users will for the most part be  
overlaying user-defined collections, not the ootb ones. The ootb  
collections are more library type collections for a specific  
aggregate of data. The user-defined collections are a way for users  
to organize and categorize their information. She believes that if  
users switch from a group of overlayed collections to one of the ootb  
collections they are switching their work mode. They don't really  
intend on overlaying the dashboard or in collection with whatever  
they happen to be looking at. She proceeds with a detail proposal  
that addresses a number of issues such as the following....

+ How we can accommodate different work styles depending on whether  
they make heavy use of user defined collections of sit in the  
dashboard most of the time.
+ The collections I overlay in one app area, may not work for another  
ie:  the overlays in the calendar app may not represent the way I  
want to work in the task app.
+ By treating the ootb collections and the user-defined ones we can  
handle some of the issues that came up in 0.6 in a more elegant way  
ie: special ootb icons and the mouse over, checkbox icons.
http://lists.osafoundation.org/pipermail/design/2006-June/004818.html


Jared posted a suggestions for improving the way in which users re- 
share their information if they are currently running a version of  
Chandler and the data on the server gets wiped. We will be addressing  
some of this as part of the data migration plan for 0.7.
http://lists.osafoundation.org/pipermail/design/2006-June/004830.html

In a related discussion, Sheila posted instructions for users to get  
their existing Chandler running against a fresh Cosmo installation on  
Cosmo Demo.
http://lists.osafoundation.org/pipermail/design/2006-June/004833.html

Continued Threads:

The discussion continued around the use of Sort. Heikki, thinks that  
people are used to having Sort available and it might be too abrupt  
to take it out. He also cited another use case (search for an email  
someone sent but no idea the subject or when) that wasn't satisfied  
by Mimi's work around suggestions. He did agree that sections could  
reduce the need for Sort.


Other discussions:

Heikki posted to the list asking users to specify the biggest  
performance issues that get in their way as they use Chandler. We are  
putting together a set of tests to use as benchmarks for performance  
work in Alpha3 and Alpha4. There were various responses but we seemed  
to converge on a proposal for a set of calendar tests to focus on...

+ Switching between calendars
+ Activating/Deactivation calendars using checkboxes
+ Double clicking to create a new event
+ Stamping events as a communication
+ Changing the view - going week to week or clicking on mini cal to  
go to a particular week
+ Synching and sharing test

For the dashboard, we will start with only a few since most of the  
features have not been implemented yet.
+ Scroll table
+ New item from menu in dashboard
+ Switch to dashboard view (from calendar view)
http://lists.osafoundation.org/pipermail/design/2006-June/004810.html

Pieter posted a link for an interesting color accessibility tool.
http://lists.osafoundation.org/pipermail/design/2006-June/004819.html

Ashkan sent out a link to a tool called Kinkless that has some  
interesting GTD related concepts.
http://lists.osafoundation.org/pipermail/design/2006-June/004820.html




-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osafoundation.org/pipermail/design/attachments/20060613/ce0a5180/attachment.htm