Wow, there's been A LOT of activity in the past few weeks. I normally
would split this up into smaller chunks, but as there were several
important threads that spanned multiple weeks, I felt it was
important to cover them in a single email.
Mimi
NEWS
We attended the FLOSS Usability Sprint this year where we got to test
the Chandler Hub web UI in a lab!
+ Katie sent out an announcement with a proposed agenda for what we
wanted to learn from the sprint. http://lists.osafoundation.org/
pipermail/design/2007-October/007784.html
+ Jeffrey recently followed up with a great FLOSS summary report
which I still need to digest and respond to. http://article.gmane.org/
gmane.org.osaf.design/8003
---
http://lists.osafoundation.org/pipermail/design/2007-November/
007859.html
We continue to make progress on the Month / Multi-week View. Reid
demo'd the latest and greatest at the staff meeting Yesterday. We
continue to make progress on complicated issues like:
+ How do we integrate navigation to and from Month View and the
navigation we currently support between Week and Day view. Our first
iteration won't have this issue fully worked out, but we've taken big
steps in the direction of having 'in-place navigation', as in, click
on what you want to look at it (Week 42 or Day 17) and in that single
click, Chandler goes directly both to that Week/Day in Week/Day-View-
mode.
+ There are still some open issues around how we dynamically adjust
the # of all-day / multi-day events we can display depending on
available space.
All-day / Multi-day discussion: http://lists.osafoundation.org/
pipermail/design/2007-October/007753.html
Bug: https://bugzilla.osafoundation.org/show_bug.cgi?id=11319
---
http://lists.osafoundation.org/pipermail/design/2007-November/
007806.html
Bobby wrote in to say that he just checked out the date picker in the
'long awaited dojo 1.0' and it's radically different in look and code
so he recommends that we wait on incorporating the date picker until
we move to dojo 1.x.
DESIGN DECISIONS
Design - http://lists.osafoundation.org/pipermail/design/2007-October/
007754.html
Users - http://lists.osafoundation.org/pipermail/chandler-users/2007-
October/000665.html
We are going to move to a model of auto-triaging events to DONE when
they pass in time with 2 additional caveats.
https://bugzilla.osafoundation.org/show_bug.cgi?id=7894
+ Scheduled tasks will not be auto-triaged to DONE.
+ Anytime and @time events are similarly exempt from auto-triaging
DESIGN ISSUES
http://lists.osafoundation.org/pipermail/design/2007-October/007686.html
Morgan and I continued to discuss 'Automatic restoration of published
shares'. In particular, how we pull down the 'default Chandler Hub'
collection when syncing the user's collections between Hub and Desktop.
Bug: https://bugzilla.osafoundation.org/show_bug.cgi?id=11320
---
http://lists.osafoundation.org/pipermail/design/2007-November/
007800.html
I logged a bug and in response to Andre re: keeping the order of
collections in sync between Hub and Desktop, which in turn sparked a
long discussion. The bug included a proposal for how to order
collections across multiple sharing accounts and multiple desktop
machines that might have different subsets of your collections.
+ https://bugzilla.osafoundation.org/show_bug.cgi?id=11244
We have yet to settle whether this is a good idea. However, I think
we *do agree* that it's really important that users can explicitly re-
order collections in the sidebar. This has been a user request since
0.6 (2 years ago!). The bug for explicit re-order: https://
bugzilla.osafoundation.org/show_bug.cgi?id=5058 is now targeted do
0.7.future, which means it's part of our near-term 3-month plan.
Next action for me: Pull together all the various sharing-related
enhancements we're undertaking into a wiki spec. http://
chandlerproject.org/Notes/PostPreviewSharingImprovements
---
http://lists.osafoundation.org/pipermail/design/2007-November/
007789.html
Dan kicked off what has proven to be a long thread about whether we
should move away from auto-resorting in ALL the columns of the table
view. Currently *only* the Triage Status column. This lead to the
unraveling of a clot of inter-related issues into separate bugs
including:
+ Renaming the Triage button in the Toolbar to Clean-up?? so that
people can figure out how to file items they've triaged into their
appropriate sections. $$$ Bug#?
+ Enabling the Triage Status column header to not only change the
sort order, but to also auto-sort items that have been triaged, but
not filed accordingly.
Whether or not to get rid of auto-resorting in all the other columns
is still an open issue. In particular, how do we background sync
happens?
Latest summary: http://lists.osafoundation.org/pipermail/design/2007-
November/007875.html
---
http://lists.osafoundation.org/pipermail/design/2007-November/
007791.html
Bobby wrote re: https://bugzilla.osafoundation.org/show_bug.cgi?
id=10759 - There are too many items in the the Dashboard on Cosmo. I
responded that I think this problem should solve itself once we
implement auto-triaging of event items to DONE on the Desktop:
https://bugzilla.osafoundation.org/show_bug.cgi?id=7894
---
http://lists.osafoundation.org/pipermail/design/2007-October/007779.html
Reid asked: Why no 'Notes-only' application area? Andre chimed in
that, indeed, this would be useful as he now has a lot of Notes. I
responded with some questions about when exactly it'd be helpful to
see 'just Notes'.
https://bugzilla.osafoundation.org/show_bug.cgi?id=11321
---
http://lists.osafoundation.org/pipermail/design/2007-October/007746.html
I forwarded an email from Edmund re: dates related to Tasks, in
particular Task due date versus Task start date. To date, we don't
have a clear understanding of how this might work in Chandler.
DESIGN PROPOSALS
http://lists.osafoundation.org/pipermail/design/2007-November/
007819.html
I sent a quick mock-up of buttons for adding and removing collections
in the Hub UI. Looks like for 0.9, we'll have a pared down 'text-
only' implementation for creating new collection and 'Remove' will be
accessed through a right-click context-menu.
---
http://lists.osafoundation.org/pipermail/design/2007-October/007749.html
I posted a proposal for how we can improve support for assigning
Tasks in Chandler. It includes changes to the Addressing fields,
byline, Who column, Communication Status column and Send/Update
buttons in the toolbar.
Mock-ups and wiki spec can be found here: http://chandlerproject.org/
Notes/EditUpdateWorkflowImprovements
Bug: https://bugzilla.osafoundation.org/show_bug.cgi?id=11030
---
http://lists.osafoundation.org/pipermail/design/2007-November/
007836.html
Our repeated discussions re: Triage Sort order in the LATER and DONE
section have now infected the NOW section as well! In particular, how
do we apply 'auto-sorting' based on custom tickler dates and event
start date/times to the NOW section *without* disrupting the current
'New and Tickled items pop to the top of the NOW section workflow'.
There's still an open issue about whether auto-sorting in the NOW
section is preferable to explicit re-ordering and/or getting a better
grip on why mixing the two is so difficult
Bug - https://bugzilla.osafoundation.org/show_bug.cgi?id=11263
---
http://lists.osafoundation.org/pipermail/design/2007-October/007757.html
In response to a number of posts to the Users list, I started a
thread about how we might expediently support allowing users to
assign 'soft-deadlines' (End of Day, Next Week, etc) to items by
adding a selection of out of the box options to the Alarms pulldown.
There are clearly lots of issues / details for Bryan and I to work
through. Most notably:
+ How are 'soft-deadlines' displayed in the Date view?
+ How often are they updated? e.g. When does Tomorrow turn into Today.
+ How are they sorted relative to items with hard-dates?
Jeffrey responded that he'd really like to be able to assign soft-
deadlines in a single gesture, directly from the Triage Status button
in the table. http://lists.osafoundation.org/pipermail/design/2007-
November/007801.html
Bug: https://bugzilla.osafoundation.org/show_bug.cgi?id=11322
---
http://lists.osafoundation.org/pipermail/design/2007-October/007755.html
After Morgen demo'd his new Twitter parcel, I did a rough pass at
what the UI might be for 'Twitter-like, ambient information'.
---
http://lists.osafoundation.org/pipermail/design/2007-October/007766.html
Brian Kirsch asked if we should take advantage of larger screens to
make sure that Chandler launches with enough screen real estate to
display the entire toolbar. There are several languages (Finnish?
German?) where our current out of the box display isn't big enough to
display everything.
Bug: https://bugzilla.osafoundation.org/show_bug.cgi?id=11316
USAGE LOG
http://lists.osafoundation.org/pipermail/design/2007-October/007773.html
Keith Winsor sent a detailed recounting of his personal usage of
Chandler with some insightful feedback. I've logged a number of bugs
to keep track of these issues. The 'conflict' resolution problem
seems like something we may want to add to our 'short list'.
Bug: https://bugzilla.osafoundation.org/show_bug.cgi?id=11317
---
http://lists.osafoundation.org/pipermail/design/2007-October/007759.html
I sent a brief description of how closely collaborating on
collections in Chandler sort of feels like having "IM for Projects".
DEMO LOG
http://lists.osafoundation.org/pipermail/design/2007-October/007781.html
Jeffrey wrote in with some 'Meeting Maker' feature ideas from a
friend he demo'd Chandler to.
Bug: https://bugzilla.osafoundation.org/show_bug.cgi?id=11318
---
http://lists.osafoundation.org/pipermail/design/2007-November/
007851.html
I responded and moved Jared's "Hub view of upcoming Cosmo work" post
to the cosmo-dev list. Many of the task items Jared listed are
currently slated for Hub 1.0.
Next action for me: Think top-down about what it means exactly for
the web UI to 'stand on its own two feet'.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
