gdb, Xcode and Chandler - a story Sounding off on design doc in yesterday’s dev meeting

tags are collections are tags?

Off and on people have been mentioning tags for Chandler items in the design list. It made me think more about “collections” and their place in Chandler.

Items in Chandler belong to one or more collections.
Items in Chandler have zero or more attributes.
Items in Chandler would have zero or more tags.

Attributes are different from collections and tags in that they have two parts: the key and the value.

The only difference between tags and colelctions is the UI. An item can have one or more tags and be in one or more collections. I find this confusing in how I use Chandler.

Now, to be sure, collections have other uses, like being shareable. However, I am wondering: should items be restricted to being in one collection? Otherwise the mental model is a bit confused between tags and collections.

On the other hand, it’s nice to be able to have items in two collections, each of which can have different sharing setups. But I wonder, should the concept of “tags” and “collections” be merged?


If it’s not clear, this entry is somewhat stream-of-conciousness, so feel free to bail.
What about making tags that are “heavy” enough to be shared? Then the UI would be the only distinction between tags and collections.

Okay, that’s enough for now.

Leave a Reply