Matthew...please scroll down for questions :)
1. Now that we have a table view in Cosmo, we need to worry about
things like 'What happens if the user commits a change to an
attribute that affects the sort order and moves the selected item off
the page the user is viewing?"
Matthew and I agreed that the 'right' behavior would be to persist in
selecting that item and displaying it in the detail view, even though
it is no longer on the page the user is on.
This is analogous to the way event-selection persists even as the
user navigates from week to week on the calendar. It also means that
if the user wasn't done editing the item, they can do so without
having to hunt it down in the list, which may be all but impossible.
2. Originally, we were planning on displaying the From and the To
attributes in the web UI dashboard. It occurred to me however that on
the whole that message items (the only kind of item with From and To
attributes) are still relatively rare and it would be a real waste of
screen real estate to devote 2 columns to 2 attributes that almost
never appear.
So, we decided to go with displaying the lastModifiedBy attributes,
which is = Updated by, Sent by, Edited by or Created by, depending on
what happened last.
For now, we're calling this column: Edited by.
3. Matthew, to be consistent with Edited by, can we change the Start
column to be Starts on?
More questions:
Are we sorting by any column other than Triage status? My
understanding was that we would only sort by Triage status. If we're
able to sort by more than Triage status, I need to produce more
buttons :)
I have updated the Stawperson Dashboard Proposal page with these
changes.
http://chandlerproject.org/Journal/
StrawpersonProposalForSimplifiedCosmoDashboard
However, the mockup on the Styleguide page does *not* reflect these
changes._ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
