Re: [Cosmo] Auto-triaging events in the web UI
Mimi Yin <[email protected]>
| Newsgroups | gmane.org.osaf.design |
|---|---|
| Message-ID | <[email protected]> |
This is truly excellent. (Assuming I understood what you wrote correctly.) On Jun 29, 2007, at 4:22 PM, Bobby Rullo wrote: > Mimi, > > A lot of autotriage/tickling is already done, as is support for > that doAutoTriageOnDateChangeFlag. More detail in line. Also, I'm > crossposting to Cosmo because there is code-y stuff in here that is > important for other cosmo UI devs. > > On Jun 29, 2007, at 3:16 PM, Mimi Yin wrote: > >> Bobby, >> >> Matthew and I reviewed the new detail view and dashboard today and >> we came across a questions re: auto-triaging. >> >> How will auto-triaging work wrt Creating and Editing items? > > Very well, thank you. But seriously. > > Creating items has similar rules to what I understand to be > Chandler's - plain jane notes get a triage as "now". Event-stamped > notes triage as the NOW, LATER, or DONE if they event is happening/ > will happen/has happened. > > Same goes for editing events, except that if the dATODC is set to > false, this triage status will never change. > > Note that the UI programmer never has to deal with this stuff - it > all happens when you apply a Delta (the cosmo ui object which > encapsulates changes) to an item. > >> Will events be auto-triaged every time the user edits the event >> date/time fields? >> > > Yup, unless dATODC is set to false. > > Incidentally, it's just called "autoTriage" in cosmo ui, so you can > just call "item.getAutoTriage()" > > >> What about the 'doAutoTriageOnDateChange' flag? I know we've >> discussed supporting it, but I don't think we ever talked about >> what needs to happen in the UI to make that work. Essentially, >> we'd need some way to tell that the user has manually set triage >> status on an item so we can set the dATODC to False. >> > > Already done. > >> dATODC should be set to False automatically when events are >> 'tickled' to NOW. >> We should also respect dATODC=False from Chandler Desktop users. >> > Done and done. > >> Should I log bugs for these two things? It might be okay to punt >> on supporting 'explicit triage' on events for Chandler Hub users. >> But I think we need to support respecting dATODC=False from >> Desktop users. >> > > We support explicit triage on events...if it means what I think it > means.... > > bobby > > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design