The Chandler Project Blog

As said in an earlier post, ref collections are implemented as a double-linked list of bi-directional item references. Ref collection indexes enhance ref collections by enabling positional access into them.

(more…)

The constructor on an Item
instance is only invoked the first time the instance is created. It is not invoked as the item is re-instantiated when loaded from the repository.

(more…)

In order to support
Item Stamping, the data model had to be enhanced to support changing an item’s kind on the fly.
(more…)

Item clouds are a way of semantically grouping together items of different kinds not otherwise stored together in a ref collection or otherwise. For example, the constitutive parts of an email in Chandler are items of various kinds such as the headers, the body, the attachments etc…
(more…)

As with the rest of Chandler, its repository is a work in progress. This is reflected in the state of the various documents pertaining to it. This post attempts to list the known and maintained sources of repository documentation.

(more…)

Ref collections, double-linked lists of bi-directional item references, are backed by a hashtable keyed on the referenced items UUIDs. Ref collections – designed with scalability in mind – are sparsely loaded into memory on an as-needed basis.
(more…)

The PyLucene project
was announced on June 24th. It started with version 0.5 to illustrate
that it was sort of half-way there; half-way to supporting the entire
Lucene set of APIs and
capabilities.

(more…)

‘redirectTo’ is an attribute aspect that redirects all value and other aspect accesses on an attribute to another one.

(more…)

It’s been 4 months since I’ve posted anything here. During this time, the repository has undergone a lot of changes I should post about.

(more…)

Recently, Jeffrey Harris wrote a paper on the Import Export Landscape and asked me to comment on it.

(more…)