New Discussions:
We held a design session on Feb 6th to review the dashboard work we
are planning for Cosmo 0.7 - Design Session: Review Preview Dashboard
Proposal.
http://lists.osafoundation.org/pipermail/design/2007-February/
006238.html
+ notes and next actions http://lists.osafoundation.org/pipermail/
design/2007-February/006241.html
Mimi followed up this email with a discussion of Cosmo-Chandler
Dashboard-Sharing issues
http://lists.osafoundation.org/pipermail/design/2007-February/
006242.html
+ Some issues that came up...
+ 1. If we don't auto-triage in Cosmo how to we deal with the fact
that these items will clutter the Chandler dashboard
+ 2. If Chandler tries to do this on Cosmo's behalf, how do we
differentiate the items that have been triaged explicitly
+ 3. Is it a problem if we don't have the same smart display of
recurring events in Cosmo (as we do in Chandler)
+ 4. Since Cosmo doesn't have a conflict resolution UI we might
overwrite changes from the Chandler user
+ Issue #4 seems problematic. After much discussion back and forth it
seems as though there is a very unique sequence of events that will
produce this issue. In fact, until we have more dogfood feedback we
don't quite now how often it will happen. The proposal for now is to
wait until we get more feedback then explore some alternatives for
mitigating the issue.
BCM forwarded an email to the list about - User Interface for Group
management in Cosmo
http://lists.osafoundation.org/pipermail/design/2007-February/
006240.html
+ Vinu is working on some group based management features for Cosmo,
he was looking for some informal design feedback. The motivation for
exploring this centers around supporting ACL work. Vinu has started
with implementing how WebDAV wants to do ACLs.
+ After some back and forth discussion it was clarified that we have
not done the full design for the general group model for Chandler and
this is not a goal for Preview nor is it meant to be. Vinu was simply
looking for some informal UI guidelines
+ BCM clarified that this feature is not even for Preview and is a
separate line of development so the design team does not have to
worry about making this a big project for Preview.
+ In the meantime, Vinu will get a bit of guidance until we have a
chance to fully design this feature for our post preview goals.
+ You don't know where the link goes until you click on it.
Heikki started a discussion about the Hyperlinks in UI. He identified
several issues.
http://lists.osafoundation.org/pipermail/design/2007-February/
006250.html
+ 1. Not all the links work and if they don't you are stuck
(particularly a problem on Linux).
+ 2. You cannot tab between them.
+ 3. You don't know what the link is until you click on it.
+ After some back and forth discussion we proposed tootips for links
to address problem #3, realizing that this will only work for mouse
users. As per our priorities for Preview we will be deferring
keyboard and accessibility issues until post-preview.
Heikki also started a thread about dialog.CenterOnSCreen()
http://lists.osafoundation.org/pipermail/design/2007-February/
006250.html
+ Heikki commented that many dialogs are using the method
CenterOnScreen() which puts the dialog in the center of the display.
He suggested using CenterOnParent() instead which makes it easier to
tell what app the dialog belongs to.
+ The consensus seemed to be to go ahead and make this change.
John started a new thread on Removing plugins and what else for Preview?
http://lists.osafoundation.org/pipermail/design/2007-February/
006258.html
+ John sent this in response to another email where Katie suggested
removing plugins as well as the test menu. The important test items
we could move to the regular menus.
+ John commented that some of the features in the test menu were
helpful for debugging and we should consider keeping it in - making
it appear based on some command.
+ Andi suggested that getting rid of plugins might not be the best
path. We could consider something similar and make them available via
keyboard/command short-cut.
+ One of Heikki's concerns was the resource usage of including them -
they slow down the app
+ This conversation was occurring on the dev list as well - katie
posted the reference.
http://lists.osafoundation.org/pipermail/chandler-dev/2007-February/
007608.html
+ People seemed to agree on a final proposal...
+ Do no remove plugins from the end-user release although we might
disable them by default and have a menu item to turn them on. Include
a test plugin menu item.
+ Remove test menu and add a tools menu
Travis posted a thread on Chandler alpha 4 delete behavior.
http://lists.osafoundation.org/pipermail/design/2007-February/
006264.html
+ He was confused about how we actually delete a collection. He tried
looking for a context menu. Then he just selected the collection in
the sidebar and hit the delete key - which deleted just a single
event. With help from people on IRC, he figured out how to select the
collection in such as way that the collection detail dialog would
appear.
+ Mimi explained some of the rational for the design. There are still
however some bugs we can fix to make this more discoverable ie:
adding a context menu and adding a menu item for specifically
deleting the selected collection.
A new thread started by John addressed the issue of Changing views in
Chandler
http://lists.osafoundation.org/pipermail/design/2007-February/
006256.html
+ After some lengthy discussion we will provide the user with 2 main
views
+ Triage table view - dashboard view.
+ Calendar view with sub options for week view and day view.
+ Search results will return in the dashboard view sorted by rank
Mimi update the dashboard spec - Please review: Dashboard Spec
Updated! with the latest set of revisions.
http://lists.osafoundation.org/pipermail/design/2007-February/
006285.html
Katie started a thread - funky freebusy fun for dogfooders to
describe a weird problem with the way Chandler publishes collections.
http://lists.osafoundation.org/pipermail/design/2007-February/
006294.html
We did some hack to publish the dashboard collections (or mine
collections) as a sub collections in Cosmo. This creates a weird
looking URL .../freebusy/... They just happened to be named free-busy
which is confusing. Now that we have released Cosmo users don't see
these collections in the drop-down list of published collections. You
can obtain the bookmarkable URL for these. This problem will exist
when Alpha4 users publish collections but will not be a problem for
Alpha5.
BCM posted a mail for Cosmo - syncing unknown item types.
http://lists.osafoundation.org/pipermail/design/2007-February/
006314.html
+ BCM gave an example of someone uploading a file into a shared
collection in Cosmo using WebDAV. When Chandler syncs, should that
appear as a spreadsheet item in Chandler?
+ We don't current have any UI to handle this anyhow, even as an
attachment.
BCM followed with another email - default attribute values for items
created by cosmo
http://lists.osafoundation.org/pipermail/design/2007-February/
006315.html
+ BCM gave another example where we can upload items into Cosmo, not
from Chandler - files, events etc. In this case, there are some
attributes that aren't set ie: triage status. He was wondering if we
wanted to set these automatically and what rules should we use.
Continued Threads:
Mimi sent out a last call for the Search - Relevance discussion to
see if there are any more thoughts on the issue.
http://lists.osafoundation.org/pipermail/design/2007-February/
006243.html
+ The proposal is to sort search results by triage status.
+ The last iteration on this discussion seemed to be debating whether
or not the relevance search was already working.
Some follow-up on the Confusion after a recurrence series is "split"
by making a modification and choosing "all furture events" thread
+ Even though we may not be able to address the issue for Preview,
Mimi logged a bug and set it to Future to keep track of the issues.
Other Stuff:
Bear sent out a link to 43Folders overview of some interesting
Stikkit features
http://lists.osafoundation.org/pipermail/design/2007-February/
006277.html
Mimi forwarded a link to the new Mail Tags Beta.
http://lists.osafoundation.org/pipermail/design/2007-February/
006296.html
+ Mimi wonders if we can update people's email their normal email
clients with mail tags._ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
