0.5 README
Welcome to Chandler!
Introduction and Overview
Purpose of Release
Chandler 0.5 focusses on building out some of the core calendaring functionality for supporting basic individual and collaborative calendaring tasks. In 0.5, you should be able to:
- Create, edit and delete calendar events.
- Navigate around the calendar in the near and distant future through the calendar summary and mini-calendar views.
- Review past and upcoming events in daily and weekly granularity.
- Collaborate on a shared individual calendar, allowing multiple authors to read, create and edit events on the shared calendar.
- Experimentally import/export iCalendar files.
In addition, the 0.5 Release provides:
- The next stage in the evolution of our developer platform with support for early adopters developers to start building parcels.
- Improvements in performance and reliability.
- Email attachment infrastructure.
- New improved sharing architecture.
- Incremental visual improvements.
Running Chandler
For OS X and Windows XP, running Chandler is very simple. You can double-click on the Chandler executable, named Chandler_osx_2005XSXX (Mac OS X), Chandler.exe (Windows XP), or chandler (Linux). If you are running Mac OS X, you need to copy Chandler from your .dmg disk image to somewhere else on your file system first.
We have made a number of changes to the repository schema for 0.5 therefore, if you have installed a previous version of Chandler, you will have to delete your current repository. More information regarding the location of your repository and the new profile directory are available at
Profile Directory.
For 0.5 we also have installers available for both Windows and Linux. These are basically compressed archives that can be unpacked to run Chandler.
Additional platform-specific information is in the README.linux.txt, README.win.txt, and README.osx.txt files included in the install process.
If you compile Chandler yourself, the instructions are slightly more complicated: see
RunningChandlerFromSourceReleases.
Setting Preferences
To use the sharing features of Chandler revision 0.5, you will need accounts on IMAP, SMTP, and WebDAV servers. The WebDAV server acts as an intermediary for Items, while email is used to send and receive invitations to share data.
To set the preferences, select
File->Accounts. You will then have a choice of setting the IMAP, SMTP, and WebDAV servers.
Email Account
For IMAP and SMTP preferences, you should be able to look at the preferences in your normal email program to figure out what the settings should be in Chandler. For "Full Name" in the IMAP preferences, use your own full name, e.g. "Mabel Garcia".
WebDAV Account
You will also need a WebDAV account to enable sharing Chandler collections.
By default a WebDAV account on the OSAF WebDAV server is selected for you. For 0.5, two other free out-of-the-box options are also being made availble from Xythos Software Inc. and Venue Communications. We are using these are "public" third-party commercial WebDAV servers to demonstrate that OSAF is not doing anything out of the ordinary to its WebDAV server in order to support Chandler sharing.
- The Venue Communications server is a demo of their WebDAV hosting service where you can subscribe to to share Macintosh iCa calendars. See Venue Communications for more information.
- The Xythos server is a demo of their Sharemation WebDAV server product. You can see more information about Sharemation at: Sharemation
If you have your own WebDAV server, you can add this account by clicking on the "Create new account" drop-down and selecting the WebDAV option.
See the Apache Foundation's
ModDAV project for more information on setting up your own webDAV server.
e.g
For a Sharemation account, for
Server, type in
- http://www.sharemation.com
For
Path, type in
IMPORTANT: Do not put a slash (/) at the beginning of the path field! That will confuse Chandler.
Requirements
Chandler uses a number of components (e.g. Python), but all the software you should need to
run Chandler is shipped with Chandler. In general, OSAF develops on Microsoft Windows XP, Red Hat Fedora Core 2, and Apple Mac OS 10.3 ("Panther").
We keep
a list of platforms that Chandler is known to build and run on. We have no reason to believe that it wouldn't work on other reasonably current versions of operating systems, but in general, haven't tested them.
One occasional difficulty is libraries on Unix machines.
If you are running with something other than a standard Red Hat Fedora Core 2 system, you
might need to either install a few modules or rebuild the binaries.
How to get involved
There are several ways that you can get involved.
The first is to
download Chandler and try it out. If you find a bug, please check the
list of known bugs in 0.5, and if it isn't listed,
report it?.
If you have an idea for a feature request, the best thing to do is to post it to our
mailing lists.
We also have a
list of small, self-contained projects -- not necessarily technical -- that
we could use some help with.
Further information -where to go to get help
For more information, please see documentation on our wiki at:
Known Major Bugs
For information about major bugs in the 0.5 release, see
License
Chandler 0.5 Copyright (c) 2002-2005 Open Source Applications Foundation
The 0.5 version of Chandler is available under the GNU General Public License,
version 2, as described in
You can also see the authoritative version of the
GNU GPL.
We expect that subsequent versions of Chandler will also be
available under one or more additional licenses. For more detail on our
licensing plans, see the
Chandler Licensing Plan.
This program is free software; you can redistribute it and/or modify it under
the terms of the GNU General Public License as published by the Free
Software Foundation; either version 2 of the License, or (at your option) any
later version.
This program is distributed in the hope that it will be useful, but WITHOUT
ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
0.6 Planning
For more on our future plans, see