Hi Sheila,
I've some comments and requests for clarification here under:
Sheila Mooney wrote:
*+ Phase #1*
*-> Goals *
- basic table support
*-> Features*
- sort
- search
- improved header
- fix a number of general table bugs
This is basically a big clean up of the Summary Table View. The biggest
item will be the integration of the wxColumnHeader (assigned to David
with some help from Robin more than likely).
I'm not sure we can have search in Phase #1 though since this is pending
changes in the toolbar (assigned to Reid). I'm assuming the UI for
search will be in the form of a search field in the toolbar...
One can imagine for phase #1 a menu item with a dialog though in order
to decorrelate the 2 issues (the UI for searching and the search mechanism).
*+ Phase #2*
*-> Goals*
- introduce triage status, ticklers and fixing the stamping cols
*-> Features*
- fix problems - who/what displays in what column
- stamping & triage status columns - no clickable icons
- mechanism to change triage status in the detail view
- ticklers
- alarms for any items
- select a custom alarm date
- dnd emails into the dashboard
- fix a few bugs to support above features
- basic sections #1
- always appear - unless you sort by a column that doesn't section
- section on triage status only - maybe date if we have time
- expand collapse
- drag and drop between sections
It seems that we may have some of this earlier (for 0.7alpha1).
I understand dnd emails as dnd between sections. Or is that dnd from an
outside application to create an event? Please clarify.
*+ Phase #3*
*-> Goals*
- add some new widgets and labelling
*-> Features*
- clickable widgets for changing triage status (summary table, detail
view)
- improved markup bar
- user editable tags - ui in detail view
- solve sidebar bi-directionality issues
- right context menu in det view label field creates a collection in
the sidebar
- dragging the text in the det view label field to the sidebar to
create a collection
- explicit ordering
- basic sections #2
- sections appear for more columns
- drag and drop to reorder sections
- empty sections appear
I'm fine with the section stuff.
For the detail view, are we talking about tags or fields? As far as I
understand, tags are like keywords, free strings with no semantic,
simply comma separated in a text field. Fields are name/value pairs and
have a more strict semantic. Tags are easy to implement, Fields require
content model work (assigned to Ted) and are quite another story. We've
been talking in other places about user defined Fields so I'm slightly
confused. I understand you want to have tags first and then (later)
fields. Am I correct?
Also, though I agree the bi-directionality issue (having items "knowing"
in which collections they appear rather than just collections knowing
which items they hold) needs to be solved, I don't understand how the 2
sub features (context click to create collection or dnd to create
collection) help with this issue. May be these 2 features were not
intended to be sub issues of the bi-directionality issue and should
simply be moved to the left.
I also understand that those 2 features are ways to create "search
collections", i.e., a collection that will have all items for which the
clicked or dragged field has the value the current item has. Is that
correct?
*+ Phase #4*
*-> Goals*
*- *advanced features so users can customize the dashboard
*-> Features*
- variable height rows in the summary table
- custom and reordering columns
- experimental sections
- user-defined attributes
- clusters of items (tasks) using sections
I understand user-defined attributes as being the Field I mentioned
above, in which case my point above is moot (or just premature).
For the moment, I'm unclear on what experimental sections and cluster of
items using sections really cover but I guess that'll be clarified later on.
Cheers,
- Philippe
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
