Chandler (software)

From Wikipedia, the free encyclopedia
Jump to: navigation, search
Chandler
Chandler-superdog.png
Chandler calendar screenshot.png
Chandler calendar
Developer(s) Open Source Applications Foundation
Written in Python
Operating system Linux, OS X, Microsoft Windows
Type Personal information manager
License Apache License 2.0
Website chandlerproject.org

Chandler is a personal information management software suite described by its developers as a "Note-to-Self Organizer"[1] designed for personal and small-group task management and calendaring. It is free software, previously released under the GNU General Public License, and now released under the Apache License 2.0.[2] It is inspired by a PIM from the 1980s called Lotus Agenda, notable because of its "free-form" approach to information management. Lead developer of Agenda, Mitch Kapor, was also involved in the vision and management of Chandler.

Chandler consists of a cross-platform desktop application (Windows, Mac OS X, Linux), the Chandler Hub Sharing Service, Chandler Server, Chandler Quick Entry for iPhone,[3] Chandler Quick Entry for Android[4] and Chandler iGoogle widget.[5] Version 1.0 of the software was released on August 8, 2008.[6]

Chandler is being developed by the Open Source Applications Foundation (OSAF). The main programming language is Python. It is named after the mystery novelist Raymond Chandler.[7]

Chandler is also the subject of the non-fiction book Dreaming in Code: Two Dozen Programmers, Three Years, 4732 Bugs, and One Quest for Transcendent Software by Scott Rosenberg.

Chandler design goals[edit]

Chandler aims to create a workflow for personal information management different from that in other PIMs. Its approach is mainly based in creating a unified representation for the storage of tasks and information so that they can be classified in a homogeneous way, refining that information through an iterative workflow, and allowing easy collaboration on the defined items.[8] Other goals include:

  • Build on open source software that supports open standards, choosing projects that are reliable, well documented, and widely used
  • Use the Python language at the top level to orchestrate low level, higher performance code
  • Design a platform that supports an extensible modular architecture
  • For the desktop client, choose a cross-platform user interface toolkit that provides native user experience
  • Use a persistent object database
  • Build in security from the ground up
  • Build an architecture that supports sharing, communication, and collaboration

Reception[edit]

The first public releases of Chandler generated expectations to provide a flexible and general information management tool, because of its heritage of concepts from Agenda and usage of principles from the Getting Things Done management method.[9][10] Early responses praised its open nature and its unified approach to management of different information types.[11] Despite this, the lack of a stable version and the small developer base diminished public interest in the project. In January 2008, Mitch Kapor announced that he was leaving the board and would only finance Chandler until the end of 2008. After that, OSAF released a 1.0 version. Jake Edge from LWN.net called this move a "last gasp attempt to build a community of users and developers to continue Chandler development down the road",[12] speculating that the lack of developers was caused by the close control of the project by OSAF, and this end of its funding could attract attention again. As of 2014, there have been no releases for over four years and the project seems to be orphaned.

See also[edit]

References[edit]

Note

External links[edit]