The list dialog continued on the issue of - Making sure the server never ends up with a big pile of untriaged Chandler items
http://lists.osafoundation.org/pipermail/design/2007-May/007338.html
+ Mimi had proposed that we automatically share triage status when the user shares a collection from the desktop to avoid the issue of having a large number of untriaged items on the server which we have to in-turn triage when we load them into the web ui in Cosmo. The Cosmo team was concerned about the performance issues of handling a large number of items with no initial triage status.
+ There were a number of objections to this proposal.
+ Some objected to always sharing the triage status by default and having to have the user "turn it off" later. There were use cases in which people just don't want to have to share it. + When users decide to not share the triage status via the manage dialog later, we will still end up with a big pile of untriaged items over time. + There were questions about why the server can't handle this since there will be items created via the Web UI or from some other CalDAV client. + The Web UI itself will auto-triage all the items it downloads from the server and there are concerns that the time to do this will be noticeable. + The real question is where we want to put the inconvenience to the user + The inconvenience for the Desktop user consists of going to the Manage share... dialog to uncheck TS after publishing. + The inconvenience for the Hub user consists of waiting a long time for data to load into the web UI. + In the end we decided to hold off on doing anything for the time being (removing the share triage option from the share dialog). We want to finish implementing the WebUI dashboard to see what the user experience is like and get some feedback on this.

Mimi sent out an Update on the Cosmo Detail View
http://lists.osafoundation.org/pipermail/design/2007-June/007351.html
+ As mentioned in previous summaries we have decided to present a slightly different detail view in the Cosmo Web UI. + Mimi has been iterating with Matthew on getting the detail view implemented. Mimi presented a summary of their process. + They will be working on this iteratively and Mimi will not be mocking up hi-res workflows and storyboards. Mimi will be looking at these iterations and tweaking them as necessary. + Mimi and Matthew talked about a number of other design tweaks not specifically related to the detail view.
+ Some of the things that will we worked on...
+ Mimi will be producing a number of new buttons for the logo, toolbar, action and confirmation buttons.
        + Mimi will rework the login links area
+ Mimi will look at PimMessageResources.properties to figure out what we can do to unify the copy across the web and desktop UIs.
+ Mimi and Matthew also agreed on a set of changes to the detail view
        + Some changes to the way we open and close the stamping sections
        + There we are a bunch of other small changes 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

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

Reply via email to