[Design] Proposal for 0.7 dashboard phases

[Mimi Yin]

Hi Davor,

This isn't an edge-case at all, I'm glad you brought it up.

So Done is a value for the attribute Triage status.
Next month is a value for the attribute Date.

Something can be both Done and Next month (ie. Taxes are due April  
15, but I've already Done them and filed them.)

I think the use case you're describing is: I want a collection of  
things that are either
Triage status: NOW or LATER; and in the NEXT MONTH.

In that case, once you've marked something as DONE, it should  
disappear from the collection because it no longer meets the Rule.

Mimi

On Mar 4, 2006, at 12:14 PM, Davor Cubranic wrote:

> Mimi Yin wrote:
>
>> Which means that "Project: Launch", has a rule that populates it.   
>> However, that rule only adds things into the "Project: Launch".  
>> It  doesn't prevent users from making exclusions or inclusions.   
>> Essentially, de-Labeling or Removing an item from "Project:  
>> Launch"  even though it is technically "From: Karen" OR Labeling  
>> or Adding an  item to "Project: Launch" even though it is neither  
>> "From nor To:  Karen."
>>
> This looks pretty reasonable in general, so I just thought I'd give  
> it a test on an edge case.
>
> What if you have a simple rule like "Next month" that collects  
> items with the due date in the next 30 days? Would it look like  
> "the right thing" if an item that a user specifically included  
> remained in that collection indefinitely? Even after it was marked  
> "done"?
>
> Should there be some visual feedback in the summary view indicating  
> items that don't match the collection rule but are included because  
> the user explicitly marked them so?
>
> Davor
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "Design" mailing list
> http://lists.osafoundation.org/mailman/listinfo/design