Assigning 'soft-deadlines' to items as a way to prioritize LATER items

So, how difficult *would* it be to implement 'soft-deadlines' as a  
part of assigning Custom Alarm Date?

Dave has outlined this in his write-up very succinctly...and I feel  
much of Andrew's feedback is in the same vein.

How about this for an OOTB set?

+ End of Day
+ Tomorrow
+ End of Week
+ Next Week
+ This Month
+ Next Month
+ In ... ( Days / Business Days / Weeks / Months)
+ Custom Date

+ We could add these options to the alarm pulldown.
+ We could easily add (in the future) an option to 'define your own'  
soft deadlines.

How would items with soft-deadlines sort in the LATER section?

Could we figure out when an item that was set for Next Week became  
something for This Week and update the Date column accordingly?

Could we figure out that something with a hard deadline of this  
Thursday should go in between items slated for This Week and Next Week?

Mimi

On Oct 18, 2007, at 3:57 PM, Dave Cowen wrote:
> Here's what I do in real life (simplified for relative brevity): I  
> sort requests by "should be done by" soft deadlines.  When I get a  
> new task, it either has a hard deadline, or I assign it a realistic  
> soft deadline:
>
> 1-4 hours from now
> Today
> Next business day
> A few business days
> End of this week
> End of the next week
> 1-2 months

On Sep 25, 2007, at 9:12 PM, Andrew Tong wrote:
> Reviewing the list, I change the first item to "now", followed by  
> changing the second item to [now] also. Since event dates are  
> ignored in the sort ordering, the result:
>
>
>   important event       [tomorrow] [now]
>
>
>   super important event [today]    [now]
>
> To overcome this, one would have to counter-intuitively flip the  
> 2nd "tomorrow" item first, then you flip the more important item.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design