Hi Bobby, > That made sense until I saw the word "auto" in your > "dateOnAutoTriageChanged" variable. Why only "auto"?
I think Mimi was confusing the boolean variable doAutoTriageOnDateChange (occasionally abbreviated doATODC) with triageStatusChanged, which is akin to a timestamp. > But otherwise, it does make sense to me that you cannot use only > "eventStart" as not everything is an event. But I think you do need to > have eventStart be part of the query because the event might not be > auto-triaged yet to "NOW" - there might not be a Chandler triaging this > event in which case it would never show up in "NOW" Hmm. Chandler puts all new items in NOW by default, unless they've got some date information in which case Chandler triages it appropriately based on its time. I can see why it might be challenging to have the server put events in DONE or LATER based on time, but I think probably you want to treat anything that hasn't been triaged yet as NOW. > What's so bad about just three events? If you really don't have that > much going on in the next week/fortnight, is it important to show stuff > beyond that range just for the sake of filling out the section? I think of the LATER section as having two big uses: things to consider working on when I'm stuck on my NOW items, and an at a glance picture of upcoming future stuff. If you limit the time range in LATER, you satisfy the latter use, but it gets in the way of the former. I hate to be a broken record on this, but I feel like being able to see all LATER items is pretty important for collections with complicated in-progress heterogenous data. I wonder if our different perspectives on this come from projecting different data sets? If we think of Cosmo as containing mostly events, then I don't think a Dashboard view is especially useful, a "this month and next" calendar view seems more useful for mostly-event data (maybe with a small table widget rendering the occasional notes and tasks without date information). The collections I'm imagining a casual collaborator finding a dashboard view useful for aren't likely to contain many (if any) birthdays or annual events, they'll mostly contain tasks and notes and a few events, some of which may be a few months out but are important to see to get a complete view of the project. If you postulate that my posited data set (although I understand we may disagree about how likely this is), does my attachment to seeing all of LATER make sense? Sincerely, Jeffrey _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
