[Chandler-dev] Renaming InclusionExclusionCollection

[Morgen Sagen]

Also, while we think of a new name, remember that one of IncExcColl's  
features is that it is "trash-aware".  In other words, removing an  
item from such a collection will place it in the trash, and as a side- 
effect remove the item from all other IncExcColls that share that trash.

I don't have a good name suggestion though.

On Mar 23, 2006, at 2:27 PM, Alec Flett wrote:

> So I think we all agree this name is just way too long.
>
> I think one of my problems with the name is that it actually that  
> it describes *too exactly* how it works rather than more  
> generically describing that it is a collection with some very  
> specific end-user behavior. I'd describe it as a collection that is  
> both a 'generated' collection as well as one that handles other  
> arbitrary ad hoc items. (i.e. inclusions and exclusions) I can  
> actually imagine that the implementation of this behavior could  
> change slightly over time, or that we'll want a slightly different  
> behavior as the end-user product evolves.
>
> So here a few semantic-free strawmen that simply imply that this  
> collection is somehow unique among the other collections:
> - SmartCollection
> - ChandlerCollection
> - AppCollection
> - DynamicCollection
> - PimCollection
>
> Votes? thoughts? suggestions? My votes would be for  
> "SmartCollection" or "PimCollection"
>
> Alec
>
>
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "chandler-dev" mailing list
> http://lists.osafoundation.org/mailman/listinfo/chandler-dev