[Sum] May 14-20

New Threads:

Priscilla posted about the Cosmo button styles
http://lists.osafoundation.org/pipermail/design/2007-May/007231.html
+ Priscilla had attached the latest button mockups to https:// 
bugzilla.osafoundation.org/show_bug.cgi?id=8560
+ This is still on the list of changes for Preview.

Priscilla started a Cosmo thread on - Draft: Consistent language on  
the web UI/desktop
http://lists.osafoundation.org/pipermail/design/2007-May/007234.html
+ Priscilla did a first pass at an inventory of all the messages and  
text on the WebUI and made recommendations for changes in order to  
make this consistent.
+ This includes terminology that we use on the desktop as well as the  
server.
http://wiki.osafoundation.org/Journal/ConsistentLanguageHubDesktop

Bobby started a lengthy thread on - Server Restraints and the Dashboard
http://lists.osafoundation.org/pipermail/design/2007-May/007238.html
+ Now that we are working on the Cosmo version of the dashboard the  
team is uncovering a number of concerns that are specific to handling  
viewing the NOW, LATER and DONE sections on the Web vs the Desktop.  
Specifically how do we deal with pulling in all this data when some  
of these sections can be quite large.
+ The issues that surfaced were....
	+ The current design has some performance and scalability issues we  
need to consider. People are worried about the performance  
implications of 		pulling in all the data.
	+ How do we look at distributing the work between the server and  
client to minimize the transfer and still show what's necessary.
	+ We looked at some proposals such as not displaying everything in  
the DONE section.
	+ We also explored time range queries for the sections.
+ The list conversation was simply an exploration of concerns and  
ideas but not concrete proposals were reached.
+ For closure - we had a follow-up meeting to talk about the options  
in more detail. http://chandlerproject.org/Journal/ 
CosmoDashboardServerConstraints20070524
+ In the end we decided to add in support for auto-triage  
capabilities which will help. The developers were working on the list  
of rules on what appears in various sections at anyone time. We will  
also only display a subset of the items in the DONE section.

Bobby also posted a Cosmo thread titled - Keep out of my dashboard!
http://lists.osafoundation.org/pipermail/design/2007-May/007239.html
+ Bobby pointed out that we have the facility in the desktop to  
include or exclude certain collections from the dashboard. He was  
wondering how this translated to Cosmo since we hadn't addressed this  
specifically in the spec.
+ Priscilla explained that there is a dashboard view of a particular  
collection and there is the main dashboard collection in the desktop  
that may or may not be shared. Cosmo will display whatever happens to  
be shared (if the user shares the main dashboard) and we are not  
constructing any special collection.

Pieter posted an issue - not sure if this is a bug - item focus is  
lost in shift from All to Calendar
http://lists.osafoundation.org/pipermail/design/2007-May/007249.html
+ Pieter navigated to an old date in the list view and then clicked  
on the calendar app area. He expected the displayed week to be for  
the old date he had selected in the list view.
+ This is an old bug that was logged and eventually punted do to the  
amount of work involved. There are also still some unresolved  
questions about getting the right design and we hope to explore this  
further after Preview.

Jeffrey posted new thread on - Not including to/from in emails from  
Chandler
http://lists.osafoundation.org/pipermail/design/2007-May/007253.html
+ Jeffrey had several suggestions
	+ We don't include to: and from: in the body of the email if they  
are actually email addresses
	+ Not add the date field if the email's date field differs from the  
date in the body.
	+ Use the format  Event details: at *location* on *date info*
+ There was agreement on fixing the first 2. Jeffrey and Mimi were  
still iterating on changes to make the format of the event details  
less confusing.

Mimi sent out a proposal for - Separate Chandler Hub and Server  
account types
http://lists.osafoundation.org/pipermail/design/2007-May/007256.html
+ Mimi suggested we have 3 account types for Chandler Hub Sharing,  
Chandler Server Sharing and WebDAV Sharing
+ We decided to get rid of the notion of default accounts because  
they are problematic.
+ OOTB we get the Chandler Hub Sharing account and the user simply  
needs to input their username and password
+ The user can choose to add a new account and select from Chandler  
Hub Sharing, Chandler Server and WebDAV Sharing. In each case, they  
will be presented with appropriate fields that need to be filled in.

Bryan Stearns send out a thread on Bug 7522: start and end time  
automagically changing wrong
http://lists.osafoundation.org/pipermail/design/2007-May/007260.html
+ Priscilla run into some issues when she tried to extend and event  
and entered a time after midnight. Since the actual time ends up  
"earlier" than the start time, we automatically change it to an @  
time event.
+ We fixed this by checking to see if the end time is changed to a  
start time AFTER 5:00pm, then we assume it's the next day.

Mimi sent out a thread asking if - Isn't the Triage Status column  
sort is broken?
http://lists.osafoundation.org/pipermail/design/2007-May/007283.html
+ She brought up the issue that when you migrate your data, the NOW  
section seems to be littered with DONE and LATER items. It doesn't  
seem to be automatically sorted by triage status.
+ There are several reasons why we have it this way - new items,  
changed, edited are supposed to be in the NOW section. Mimi created a  
bug to track this post-Preview with more user feedback. https:// 
bugzilla.osafoundation.org/show_bug.cgi?id=9175

Mimi posted about an issue - Triaged items keep re-appearing in NOW  
when I sync
http://lists.osafoundation.org/pipermail/design/2007-May/007291.html
+ This is something that is still an issue. We have fixed some of the  
problems but there are issues with recurring events. I believe we are  
checking in a bunch of fixes this week that will address most of  
these bugs.

Priscilla sent out an Update on the Cosmo 0.7 spec
http://lists.osafoundation.org/pipermail/design/2007-May/007296.html

Mimi posted a few thread on -  Time zone options - A little bit o'  
options can be a dangerous thing...
http://lists.osafoundation.org/pipermail/design/2007-May/007298.html
+ Mimi discovered a few user issues maintaining shares calendars  
where some events were in NY time and some in LA time. She  
articulated some weird use cases when other people subscribe and turn  
on timezones.
+ We are not attempting to solve this issue in the Preview timeframe  
and Mimi has logged a bug to track it. https:// 
bugzilla.osafoundation.org/show_bug.cgi?id=9208

Mimi sent out a summary of all the bugs we found in our Friday - PPD- 
QA Edit/Update Testing Session
http://lists.osafoundation.org/pipermail/design/2007-May/007307.html

Previous Discussions:

Mimi sent out a last call for the thread - when Dashboard does not  
equal Dashboard
http://lists.osafoundation.org/pipermail/design/2007-May/007259.html
+ Pieter had previously restored his shares and since he had shared  
his main dashboard and ended up with 2 of them when he restored.
+ For Preview - if you share an OOTB collection then migrate via dump  
and reload you will see the collection duped because we can't synch  
up the OOTB  collection that was shared and the new one created when  
you reload.
+ Non shared OOTB collections should work fine.
+ In the end we resolved this because OOTB collections CANNOT be shared.

Other Stuff:

Davor sent out a link to OmniFocus beta
http://lists.osafoundation.org/pipermail/design/2007-May/007267.html

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design