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. 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. Sheila sent out the first draft of the 0.7 sidebar spec to the list. 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. Sheila sent out a draft of the Alpha4 Dashboard spec for review. 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. 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. In a related discussion, Sheila posted instructions for users to get their existing Chandler running against a fresh Cosmo installation on Cosmo Demo. 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) Pieter posted a link for an interesting color accessibility tool. Ashkan sent out a link to a tool called Kinkless that has some interesting GTD related concepts. |
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
