[Design] Re: implementation ideas for "sections"

[Mimi Yin]

Features needed to establish a framework for the Triage workflow:  
(this is stuff beyond basic table)
+ Ability to define focus (Now, Later, Done)
+ Ability for users to tweak focus (Now, Today, Tonight, Later, Done)
+ Ability to "put" items on lists via Labeling (ie. @Juno, Project:  
Foo, Calls list)

User scenarios for Stage 2 Dashboard with "Sections":
===
Jim is in a meeting with Kario and would like to see both his @Kario  
list and the list of items he's been maintaining for each of the  
projects he and Kario work on together:
+ @Kario
+ Project: Learn Kanji
+ Project: Buy a notebook

Option 1 to meet this use case
+ Add these 3 lists to the sidebar
+ Overlay these 3 lists
+ Summary pane splits into 3 panes, 1 for each list with independent  
scollbars

Option 2 to meet this use case
+ Provide affordances to let user defined sections based on a mix of  
attributes in a single summary pane. Sections would *NOT* be tied to  
a single column.

Some sections might be:
+ Triage status: Now
+ Project: Foo
+ @ Karin
+ @ Work

===

SECTION BY COLUMN OPTION
+ Allow sectioning by any column displayed in the summary pane: Who,  
Date, Stamping columns, and any columns the user defines
+ User clicks on a column to section by that column

Some "Section by column" user scenarios
+ To aid in search and scanning
+ To view threads of items
+ To review all of your projects in a single view

Mimi

On Feb 2, 2006, at 10:06 AM, Mimi Yin wrote:

> Forwarding an exchange about progress on Sections to the  
> list...will follow-up with an email outlining the different  
> "options" we're considering for sectioning the table in 0.7.
>
>
>> On Feb 1, 2006, at 5:16 PM, Mimi Yin wrote:
>>
>>> Wow, that was unexpected...just to clarify...I'm not proposing  
>>> "no sections". I'm proposing that we use the sidebar as a way to  
>>> show and hide sections. I was trying to get at the root of  
>>> Mitch's proposal and looking for some other implementation ideas  
>>> at the same time.
>>>
>>> Maybe we can have a quick conversation about this after the staff  
>>> meeting tomorrow.
>>>
>>> Mimi
>>>
>>> At 4:39 PM -0800 2/1/06, Alec Flett wrote:
>>>> Thanks Mimi -
>>>> From the engineering side, I've got an update: I've actually got  
>>>> a really really barebones implementation of sections in the  
>>>> table summary view.. here's a screen shot of it in action:
>>>>
>>>> This may not look like much, but this demonstrates the plumbing  
>>>> required to make this happen. Specifically, the "section header"  
>>>> just makes each column in the header say "[Section: foo]" - and  
>>>> this is working for any arbitrary value at the moment, so what  
>>>> you see is sectioning by triage, but you can click on who/about  
>>>> and get sections based on them too.
>>>>
>>>> What's left here:
>>>> 1) drawing something better than [Section: foo] in each cell -  
>>>> we can probably rig something up pretty easily with attribute  
>>>> editors
>>>> 2) making section rows exapandable/clickable/etc
>>>> 3) lots of little odd bugs
>>>>
>>>> I'm still not sure I completely understand Mimi's proposal, but  
>>>> I'll take that up on the design list.... but if sections as you  
>>>> wanted were, say, halfway there, would the alternative non- 
>>>> sectioned triage design still be relevant?
>>>>
>>>> Alec
>>>>
>>>>
>>>> Attachment converted: Lamby:sections-basic.png (PNGf/ogle)  
>>>> (00059C26)
>>>
>>
>
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "Design" mailing list
> http://lists.osafoundation.org/mailman/listinfo/design

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osafoundation.org/pipermail/design/attachments/20060202/89c7e327/attachment.html