[Chandler-dev] Dashboard domain model questions

[Andi Vajda]

On Thu, 29 Jun 2006, Bryan Stearns wrote:

> My concern was about the conflict that we've got a sort order already (see 
> above example), and I'm not sure how to represent manual ad-hoc additions to 
> it in the indexing mechanism, in an environment where items are moving around 
> in the index automatically relatively frequently (as their triage status 
> changes with the passage of time). If I manually position something to be 
> first in the Now section, and three ticklers go off (moving their items to 
> the top of the Now section because they have the most-recent triage-status 
> change date), what piece of information causes that manually-positioned item 
> to now be 4th? (Or is it still first?)

Oh, you mean to inject user chosen order into an otherwise programmed sort ?
Uh, that's a little harder...
One could imagine that the last criteria by which items are sorted is 
arbitrary, or user chosen. By this, I mean that once all other sort attributes 
have, in order, returned 0 (==), then the manual user chosen one could be 
applied to sort the ones that are == by all other criteria.
What I don't see how to do offhand is arbitrary user order injections anywhere 
in the index.

Another way to maybe think of this is displaying two collections, the 
user-sorted one first and then the program-sorted one ?

Andi..