[Design] Remove behavior

[Davor Cubranic]

Jeffrey Harris wrote:
> Presumably your FYI's and not-super-urgent tasks aren't done, or you'd
> mark them as such, right?  If you could remove those items from the
> dashboard, where would you want to see them?
>   
Their originating collection. To me, collections are organized by 
context (e.g., Home vs. Work), and so contain both important and 
unimportant (e.g., FYI) items. Dashboard to me should be the birds-eye 
view of the important stuff, which is why excluding some items from it 
would be nice. (Even if exclusion is not defined per item, but rather is 
based on some other attribute, like "status".)
> The Now-Later-Done dance is, happily, fixed on the trunk.  Now nothing
> changes its position until you click the "Triage" button.
>   
I actually like the automatic triage, there is something very visceral 
in its immediate response. It's just when I wanted to switch to Later 
that it was a pain. But I'm looking forward to trying out the new 
version, I think it beats losing the context as it happens in 0.7a4.
> Definitely having the Now section filled with irrelevant recurring
> events makes the dashboard less useful.  Once that's fixed, do you have
> ideas of ways you could make long lists of Now items more approachable?
>   
Not really, as long as Now and Later are the only two active states and 
items can only be filtered by collection. (Not that there is anything 
wrong with it.) Having an "on-the-fly search" box that filtered items 
shown in the summary view, like in iTunes, would be insanely cool though.
>> On the other hand, defining a tickler for a Chandler task is done by
>> attaching a custom "alarm" and requires setting up a time (why?).
>> More importantly, it doesn't let me distinguish between different
>> types of ticklers.
>>     
>
> Can you explain your "(why?)" a bit?  Do you mean you just want to be
> able to set a day for the alarm, but no time?
>   
Yes, that's what I meant. My tasks in general need to be done by some 
particular day, time doesn't matter. What would be nice is to have a 
"target date" (and optional time) associated with a task, which is what 
would appear in the Date column in the summary view. Target date could 
be turned into an alarm, but wouldn't have to be -- I don't need a popup 
for every deadline I let woosh by. :-) Tasks that aren't completed and 
are due "today" should perhaps appear in the minical (or somewhere else 
in the calendar, I'm just not sure where, as the "all-day" section is 
pretty tight), with overdue tasks carrying over until marked done. This 
is almost doable already by using items stamped as both tasks and 
all-day events, except for the part where they are filtered out of the 
calendar once marked "done".
>> One more thing: the layout of the summary table in the Tasks area is 
>> wasting a lot of space for things that are irrelevant to it, like the
>>  Who column, while there is hardly any room for the task description.
>>     
> The Who column will be used for emailed items, it's true.  It'll also be
> used for keeping track of who last changed a shared task.  When that's
> working I think it should help the who column seem like a good use of
> screen real estate.
>   
I can see this being useful once multiple people are working on a task. 
BTW, it might be nice to have columns that can easily be collapsed to 
just a few pixels wide, or whose order in the table can be rearranged. A 
future enhancement, perhaps?
> Perhaps a useful addition for collections where there's no Who to show
> except "me" would be to collapse the Who column?
>   
Sure, that would be perfect.

Davor