A problem in the "Reload Collection and Settings" limited to Mac PPC prompted us to release a 0.7.2.1 bug fix for that platform. If you are using 0.7.2 for Mac PPC and had problems migrating your Chandler data from a previous version, please download 0.7.2.1.
Here are the minimum and recommended configurations for running Chandler Desktop:
Chandler Desktop Release Notes
These Release Notes give a near complete but condensed list of the major modifications that happened in Chandler Desktop since Chandler 0.6. It doesn't list all bug fixes, neither does it describe all architectural changes made to the build, test architecture and development tools as it is focused on changes that have an influence on Chandler users and the Chandler experience.
Improved and New Features
Triage Table and Dashboard
- The Triage Table is the default way of displaying and interacting with items and can be used for all kind of items, including events. The default All collection always shows that view even when the Calendar is selected in the toolbar. Also, that collection is renamed Dashboard (formerly My Calendar) as it now contains any kind of items.
- A Triage column and Triage button have been added to the User Interface. Any item can be triaged for NOW, LATER or DONE. Events and items with reminders are automatically triaged so to show up in the right section. Modified shared items show up in the Now section when modified even if their triage status is not Now so to notify the user that a change happened. Items can be triaged in place in the table without confusingly moving around. The toolbar Triage button gets everything back in the correct section.
- The table widget used by the Triage Table has been improved: better native table headers, better sorting on columns (ascending and descending), separation of the table in collapsable sections (for triage only in Chandler Preview), state icons with tooltips in columns, in place editing for some columns (triage, communication status, reminders).
- The Who and Date columns display the latest updater and next useful date respectively. Similarly the detail view of an item displays a byline field showing who and when an item was last modified.
- Sharing with Chandler Server is much more reliable and faster using the new Morse Code protocol. Any kind of item can be shared through Morse Code.
- The sharing Ticket URL is unique for all use: it can be used to subscribe to a collection from another Chandler or directly from a browser using the Chandler web client.
- Chandler provides default connection and settings for sharing on the free chandlerhub service. User must create an account and give their user name and password in the
- If you run your own Chandler Server instance or have collections hosted on another Chandler Server, use the
File>>Accounts... and create a Chandler Server Sharing account.
- Merging of items edited by different people on Chandler Server or shared via email has been implemented. Concurrent edits do not overwrite each other anymore.
- In case of conflict in concurrent editing, a conflict management dialog is provided to the user so no data is accidentally lost.
- Chandler offers automatically scheduled sync done in the background without impairing the use of the application.
- There's an offline mode available from the menu so to explicitly prevent sharing if needed.
- Sharing of individual items is fully supported using email as a sharing conduit. No Chandler server is necessary is that case (see Email here under).
- The Never share per item option has been removed as it was too confusing for users (too similar to a read only feature) and was too difficult to track. To avoid sharing an item, you need to move it in a collection that is not shared.
- The account setting dialog has been deeply modified and simplified. An auto configure feature allows most common email settings to be automatically discovered by Chandler.
- A new Edit/Update workflow has been implemented: this means that any item, including emails inbound or outbound, is editable and can be sent again (aka Updated) to its originators and addresses. This workflow does not create a thread of items but allows one item to be shared and modified using email as a sharing conduit. We hope to promote this workflow as an alternative to long threads when working collaboratively on a task/event/note item.
- Despite its improved support for IMAP, POP and SMTP and because of its specificities (Edit/Update workflow, no notion of hierarchy of folders, all items editable, items morphing into other kinds, etc...), Chandler cannot be considered a full fledge email client. In particular, emails downloaded on Chandler using IMAP do not disappear from Chandler when deleted on the mail server. Symmetrically, emails deleted on Chandler are not deleted on the server. You should be aware of these particularities if you intend to use Chandler as an email client of sorts.
- Chandler also supports the more traditional Reply, Reply all and Forward set of buttons. Replying to an email creates another item instead of modifying the working item (use Update to prevent generating new items). Chandler implements from, to, cc and bcc addressing fields.
- Chandler can receive any email but only emails sent by other Chandlers are automatically downloaded. In that case, Chandler shows the item in its full Chandler glory, i.e. with all its fields and attributes carried along. In such a scenario, email is simply a conduit to exchange full fledged Chandler items between Chandler clients, without having to sync up with an intermediate Chandler Hub.
- Additionally, Chandler can receive any email from any client but only if those emails have been dropped in a special set of IMAP Chandler folders. Those folders are created when setting up the email account in Chandler. Email passed through those folders are marked as Tasks or Events depending in which folder they are dropped in. Email with simple dates in their title are automatically recognized, parsed and marked as events by Chandler. See the Getting Started Guide for more on this and other new email functionalities.
- ICS attachments are automatically converted into Chandler events and, symmetrically, Chandler events are attached as ICS when emailed. This allows Chandler to support a very basic invite workflow. Chandler does not support iMip/iTip though. Also other attachments are not yet converted into Chandler's item (e.g. attached vCards) and Chandler does not support attached files.
- The calendar rendering has been improved to be more pleasant: rounded corners, new colored gradient, white text and better typography, color swatches for items presents in several user collections.
- The number of hours displayed per day (vertical spread of events) can be changed under the
View>>Visible Hours menu.
- Several aspects of the User Interface (Drag and Drop, scrolling, keyboard navigation) have been improved or added.
- Date entry fields auto complete for quick entry and support parsing of natural language date and time (e.g. "Monday" will set the date for next Monday, "tomorrow" for tomorrow, "lunch" or "noon" will set the time to 12:00PM).
- Print was too deficient and has been pulled out of Preview.
- Free/busy, which was experimentally introduced in 0.7alpha3, has been pulled out of Preview as it was not robust enough and was not clearly useful without support for contacts.
- Menus have been rearranged so some commands may not be in the same place as in Chandler 0.6. Accelerators and shortcuts have been more consistently implemented.
- Most places in the application support a contextual menu (right-click or control-click depending on the platform).
- Experimental features and developers tools have all been segregated under the
Tools menu. Some of these new experimental features are a repository servlet to view items in a browser (e.g. hit
F4 to browse into any item), repository check and repair tools and a script recording and script player tool among others.
Security and Troubleshooting
- It is possible to encrypt the entire repository or just email and sharing passwords and control access with a master password.
- When a crash happens, Chandler displays the traceback in a pop up feedback dialog and allows the user to email the trace to OSAF.
- In some situations where the repository is in a bad state, Chandler provides a set of options to try to repair the troubled database. Launch Chandler with the Control (Ctrl) key depressed to see this Control Startup dialog appear and the available set of options.
- The repository is compacted on a regular schedule (every week) to improve Chandler's performance and reliability.
- Chandler can export and reload an entire repository in a new format (
.chex) based on EIM (see EIM in the Architecture section).
- This format is guarantee to work between revisions (as opposed to the repository itself) so you can use it to save your data and migrate to a new release of Chandler or to a new type of machine (e.g. from Windows to Linux).
- The Preview version however does not export certificates and data generated by plug ins. If you are using some of the plug ins, be aware those those data will not be migrated between versions.
Quick Entry and Search
- Chandler sports a text field in the toolbar that allows for the quick creation of new items using a simple syntax:
- Chandler automatically extracts date time using a simple natural language parser and makes its best guess on fuzzy date (e.g. "/e lunch Thursday with Bob" will create an event on the next following Thursday at 12pm).
/find launches a search on the repository. Chandler search relies on PyLucene for string match and supports Lucene query syntax for advanced searches.
- The sidebar has been significantly reworked, supporting on-hover animation, status icons with tooltips, etc...
- An expandable preview area, giving a summary of the selected or current day, has been implemented. Events on this preview area can be clicked and selected.
- Drag and drop between the calendar and the minicalendar allows moving events around from a week to another.
- The sidebar is resizable.
- The In and Out collections always show in the sidebar.
The Chandler Desktop source code is available under the terms of the Apache Software License, Version 2.0.
With Preview, Chandler expanded its support for iCalendar, implementing VTODO support for instance and fixing numerous import/export issues with ics files produced by a variety of applications. Chandler Preview calibrated its interoperability mostly with Apple's iCal. We are aware of bugs with ics produced by other applications that we intend to address in an upcoming Chandler Desktop 0.7.1 release. Though Chandler Desktop uses morsecode to exchange data with Chandler Server, Chandler Desktop and Server both continue to support CalDAV and WebDAV.
Though we acknowledge there's still lots to do, Chandler performance has been improved in many areas: event notification, UI drawing, sharing, email, etc... As a result, Chandler is able to handle real life scenarios with sizable collections of items and email inboxes. Chandler performance will continue to be one of our focus in the coming releases.
The Schema API has been cleaned up and changed significantly since Chandler 0.6. If you wrote any parcel for Chandler 0.6, you will likely have to revise your code. See the application.schema module in Chandler API to view the new API and the Schema API Guide.
The stamping idea is very central to Chandler. This is the thing that allow an item to be several things at the same time (e.g. an event and a task). The underlying model for stamping has been completely redone in Chandler Preview. See the seminal discussion for the reasons of this change.
EIM stands for External Information Model. It is a schema independent representation of data that is well suited for exchange of information. Currently, Sharing, Import/Export, Export/Reload, and Share-by-email all use EIM. EIMML is an XML representation of EIM records, and is used by sharing over Morse Code as well as by Share-by-email when sending Chandler items over email. Import/Export currently converts EIM to ICS format, but other formats could be used in the future. Export/Reload uses the Python "pickle" format to save EIM records on file. See our EIMML Spec for more on EIM.
Chandler uses unicode strings, translation services and PyICU consistently. Localized resources are packaged as Python Eggs and distributed off Cheese Shop. A set of tools have been created to extract
.pot files and package translation eggs. All localizable resources (images, html files) have been moved to the
Chandler.egg-info/ structure. Some issues though still prevent Chandler Desktop to be easily localizable and Chandler Preview is using a Chandler-en.po file to provide better English strings to the end user. We are planning to fix this and other reminding i18n issues in an upcoming Chandler Desktop 0.7.1 release. For more info on localization see our Localization project page.
Plugins are optional extension modules formerly known as "parcels". They are packaged as Python Eggs and made available through Cheese Shop (Python Package Index). Some experimental plugins are already available for download (see
Plugin>>Download menu in Chandler or directly on Cheese Shop). The Feed plugin, used in the tutorial, has been updated to work with the new architecture. Please, see that tutorial to learn more about these changes. Plugins are downloaded into the
plugins/ directory and installed into the
projects/ directory, outside the
parcels/ directory. Note that Chandler still continues to use the "parcel" wording internally. "Plugins" is used only when talking about 3rd party, optionally installable and downloadable functionalities. Be aware that, because of their experimental nature, those plugins have not been tested regularly and can corrupt your repository. If you end up with a corrupted repository, please go to the troubleshooting page for several tips on how to get your repository back in a consistent state. Also, as a safeguard against propagating corruption, the export/reload feature does not save the data generated by the plugins, in other words, data generated by plugins will be lost when migrating to a new version. We plan to address those issues in an upcoming release.
Command line arguments
For developers launching Chandler from the command line, there has been a long list of arguments added to Chandler Desktop to cover a variety of debugging, troubleshooting and test situations. For instance, you can repair a broken repository with
--repair, launch Chandler in a specific language with
--locale or even undo some repository version with
--undo. Use the
--help argument to get the list of all available options.
Chandler ships with slightly modified Python 2.5.
Chandler Server 0.8 Release Notes
These release notes provide a condensed list of the major modifications to Chandler Server (Cosmo) since the Cosmo 0.7 release.
Improved and New Features
Support for Safari 2.0
All known bugs with Safari 2.0 have been resolved.
CalDAV? support and init"> Improved CalDAV support and initial support for iCal 3.0
Improved compatibility with the CalDAV RFC.
iCal 3.0 (in Mac OS 10.5 "Leopard") will work with Chandler Server 0.8.1 with the following caveats:
We are working with Apple to improve compatibility with iCal 3.
- Collections with spaces in their names do not work with iCal3 - this includes the "Out of the box" collection created for a new user of Chandler Server. iCal 3 users can create their own new collections on a Chandler Server instance without problems.
- Events which are stamped as tasks show up as neither
- Some collections do not appear
See the known issues list for specific about
current known issues, bugs, and limitations.
The web interface supports Firefox 2.0, Safari 2.0, IE 6, and IE 7.
The Java-based server code and the provided server bundle should run
on any Java 1.5 runtime environment.
The Chandler Server source code is available under the terms of the Apache Software License, Version 2.0.
-- TedLeung - 30 Oct 2007
Chandler Hub changes
- Our primary server has been upgraded.
- The server compresses Ajax server responses to boost performance.
- Support for earlier
/home DAV URLs has been dropped. Use the
/dav replacement URLs instead.