Ok, the last thing...
I'm confused, the text you quote from the spec, to me, says the same
thing as what I wrote in my last email.
Explicitly marking triage status ONLY TURNS OFF auto-triaging
triggered by people actually change date/time information on an item.
It DOES NOT turn of auto-triaging triggered by time passing, aka
tickling.
I will try and find you on IRC to straighten this out.
Thx!
Mimi
On Feb 16, 2007, at 8:47 AM, Bryan Stearns wrote:
Note that this is distinct from the similar case of an alarm
firing on an event just after the user had clicked on a triage
widget: that case would never pop to the top when the alarm fires
because we turn off auto triaging when the user creates an
unpurged state by clicking on the widget, remember?)
Doh!? We turn off auto-triaging based on the user assigning and/or
changing date/time information on the item. We never turn off auto-
triaging based on time passing, aka tickling. So if I explicitly
triage something to LATER, I still want the item to pop-back into
NOW automatically when the alarm fires.
Yes - I put this in because your spec clearly says so: "Caveat:
Auto-triaging triggered by users assigning and changing date/time
information to items stops if the user 'explicitly' triages the
item by either:
* Clicking on the triage status button in the mark-up bar or the
triage column in the Dashboard
* Item is triaged to NOW because and alarm fires or event date/
time passes"
But since you're now saying you don't want that, I've updated my
spec to reflect this.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
