[Design] [Sum] April 31 - May 14

[Sheila Mooney]

New Design Discussions:

Mimi sent out a survey for the number and flavor of recurring events  
people have on their calendar. We intend on using this info to build  
a test data set for the performance scenarios.
http://lists.osafoundation.org/pipermail/design/2006-May/004679.html

Mitch posted some suggestions for reducing the default number of  
hours display for improved display of time and title information,  
particularly for 30 min events. Further discussion followed. Mimi was  
concerned about users with smaller screens and still feel 1 hour  
events are most common. Jeremy suggested moving the "window" of view  
as the day progressed which doesn't address a persons need to see an  
overview of the day. As Matt pointed out, this problem exists in the  
web client as well as the desktop client. Mitch pointed out that we  
probably need concrete statistics on screen size and the ratio of 30  
min vs 60 min meetings but having something that can intelligently  
pick a default would be good alternative.

Mimi sent out a proposal for further enhancements for the mini cal.  
Jed had addressed many of the existing bugs but there were still some  
issues that we need to address for improving the readability.
http://lists.osafoundation.org/pipermail/design/2006-May/004717.html

Esther posted about having the ability to track changes as they are  
made to the calendar. When there are multiple people editing, we need  
to have some kind of summary of when the changes were made and by  
whom. Several people seconded this request and there were a few ideas  
discussed ie: special visual affordances in the calendar and summary  
view when something has changed, rss change logs. A notification  
mechanism is currently on the plan for 0.7 and the design team will  
be tackling a more concrete proposal, with discussion of options in  
the near future.

Dan posted about making the mine and not mine feedback more obvious.  
The current visual affordances are not intuitive enough. Since we  
currently don't have the notion of spheres fully realized this was a  
compromise. The design team will revisit this and look at some better  
alternatives for 1.0 that solve the problem but don't rely on a full  
scale spheres implementation.
http://lists.osafoundation.org/pipermail/design/2006-May/004731.html

Mimi took some comments Alec had made in another discussion and  
spawned a new thread about the use of the All Collection. She  
explained that our notion of All was really the central Dashboard  
where users would get the runway view of their life and we expect  
them to spend most of there time there. Further discussion continued  
around what will happen as this collection grows and the better  
portion of the items will be the DONE state and we don't really want  
to see them anymore. Mimi explained that we would try and keep the  
DONE section out of the way but still there if the user needs to  
search or get access to the information easily. She also brought up  
the ability to archive some of these items into a special collection  
- we talked about this a while ago. There was mixed reaction to the  
archive collection but we seemed to be converging on some options to  
keep the DONE there but not in the way.
http://lists.osafoundation.org/pipermail/design/2006-May/004734.html

Continued Threads:

Further discussion continued around the lozenge shape specifically  
the subtleties of visualizing event status with dotted lines around  
the event and how this may conflict with people's visualization of  
focus for web apps. Mimi followed up with some visual tweaks in  
several rounds of iterating. The discussion continued further around  
the conventions for web apps in general to handle focus and selection  
and how we may not have control over this for Scooby. It seems as  
though the discussion reached a general consensus and Mimi will send  
out a final palette design.

There was further conversation around the ability to support  
partially filled events that users can iterate on before they have  
the final details. Philippe pointed to a real use case in trying to  
schedule a meeting during sprint week. He did point out that if we  
send these to other clients, they may not be able to interpret them  
so we need to be aware of the interop issues.

General Posts:

Sheila sent out a wiki page with the alpha3 plan or record.
http://lists.osafoundation.org/pipermail/design/2006-May/004720.html

Sheila also sent out a list of the 0.7 dashboard performance scenarios.
http://lists.osafoundation.org/pipermail/design/2006-May/004722.html

Ted sent out a blog post about Google synching to outlook and iCal.
<http://googlesystem.blogspot.com/2006/04/google-calendar-to-include- 
outlook.html>

Ted sent out a link to a couple of articles on email and collaboration.
<http://blog.centraldesktop.com/comments.php? 
y=06&m=05&entry=entry060501-194015>	


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