Chandler software development
Overview: three major projects with a common data model, sharing framework and external information model
Chandler comprises three projects:
At the core of the common data model is the |
Item class. Related attributes are added or subtracted by stamping
Within the sharing framework the EIM (external information model) layer mediates between Chandler objects and their external serialised representations
- example: an event stamp adds date information to a note item.
Apache License, Version 2.0 applies.
- example: Chandler Desktop 1 uses the EIM-based Chandler exchange format to save a
backup.chex file whenever the application quits.
What to hack on
Chandler 1 is the code base for the 1.x desktop product. Releases of Chandler Server and Chandler Desktop 1.x are stable.
Since March 2009, all development is volunteer and most is towards Chandler 2 — the future of Chandler Desktop. This project is under construction and all forms of help are encouraged!
Some pages in the wiki are naturally outdated. The short history of the three projects is recommended reading.
If you use Chandler 1 and would like to fix a bug, go for it! Otherwise, focus on Chandler Server and Chandler 2.
Built on Tomcat, Hibernate, the Spring Framework, Acegi Security for Spring, iCal4J, Dojo, Abdera, Jackrabbit, Woodstox, and other best of breed technologies.
Client access to Chandler Server data
Whilst many CalDAV clients are supported, being a reference implementation is not a priority.
Written in Python, building on Twisted for networking services, Berkeley DB for storage and wxPython for the GUI framework.
Chandler Desktop 1.0.3:
- uses Cosmo Morse Code to discover collections on a Cosmo server
- does not automatically discover collections on a CalDAV server (instead: the application may be subscribed to URL of each collection)
Written in Python, loosely coupled to wxPython for the GUI framework, based on Trellis. Ready for hacking on — limited UI, import and export of .chex files. (Not for end users — no packaged installers, no persistence.)
An instance of Chandler Server provided by the Open Source Applications Foundation (OSAF)
Hosted or maintained by OSAF staff members, partially funded by OSAF, or in some other way directly related to the Foundation:
A more complete list of contributions to other projects personal injury protection.
Wikis: updates and obsolescence
Don't assume that every page is up to date! Alongside the Chandler Project blog, which began in 2003, this wiki provides a historical record of developments. Pages relating to Chandler 1 may be particularly outdated.
Questions and clarification
For clarification on any subject, please address the mailing lists or chat with us on IRC.