Archive for December, 2007

Chandler Server (Cosmo) 0.10.1 released

December 7th, 2007 at 11:45 am (5 months ago) by Ted Leung under Chandler Server Development

The Chandler Project is pleased to announce the 0.10.1 release of Chandler Server (Cosmo)!

Chandler Server is a server and Ajax web UI for managing and sharing calendars, events, and tasks. It implements open data standards including CalDAV, WebDAV, Atom, and Atompub.

This is a security bugfix release for Chandler Server 0.10 and we recommend that all users upgrade to this version.

Chandler Server 0.10.1 is currently available for download as a ready-to-run bundle at:

     chandlerproject.org/serverdownload

and the source code is available from subversion at:

     svn.osafoundation.org/server/cosmo/tags/rel_0.10.1

Send us feedback at the open mailing list:

     chandler-users at osafoundation.org

We look forward to hearing from you!

The bugs fixed in this release are:

11587 Dav users can create resources within other users’ home collections

A summary of known issues in this release is available:

     chandlerproject.org/knownissues

There was no change to the database schema for Chandler Server in version 0.x. Instructions for upgrading from previous versions of Chandler Server can be found at: <http://chandlerproject.org/Developers/ServerBundleInstallation#Upgrading%20from%20previous%20versions>


Chandler Desktop 0.7.3 Released

December 6th, 2007 at 11:03 pm (5 months ago) by pbossut under Chandler Product News

The Chandler Project is pleased to announce the 0.7.3 release of Chandler Desktop!

Download link, information on mailing lists, and how to get the sources available from the homepage.

The 0.7.3 release is the third in a series of quick, time-based releases since Chandler Preview 0.7.0 intended to respond to the feedback we received from 0.7.0 and continue to receive from these quick releases.

0.7.3 fixes over 50 bugs and includes some major improvements:

  • Month View:Yes! Month View! This has been pretty much at the very top of everyone’s wish list so we decided to bite the bullet and just did it. Month View can be reached by simply clicking the month name in the top area of the calendar. Switch back to week view simply clicking on the week number on the left side. This fixes bugs:
    • Bug #5361: 30-day view? Variable multi-day view.
  • Bundled Localizations: Chandler now comes bundled with localizations in French, Swedish and Finnish. If you’d like to join the localization effort in your own native language, we are looking for volunteers. This is a great way to get familiarized with Chandler ideas and its community. We fixed the following bugs along the way:
    • Bug #11197 Normalize dialog title capitalization
    • Bug #11199 Bogus message in MasterPassword
    • Bug #11201 Incorrect strings in GetPasswordDialog
    • Bug #11260 Export dialog text says ‘Exported’ not Dumped
    • Bug #11333 Reword Unpublish Confirmation dialog
    • Bug #11405 Need different strings for no encryption and no alarm (currently ‘None’)
    • Bug #11419 Fixed running with localed using ‘,’ instead of ‘.’ for decimal point (was : invalid literal for float() error when reloading a .chex)
    • Bug #11470 File > Sync manager… has mnemonic
    • Bug #11490 Reminders dialog missing mnemonics, default button
  • Share Management: There’s a new feature under the File menu called Sync Manager. This allows users to view and choose which of the published collections on their Chandler Server need to be synced with the Chandler Desktop. Additionally, this dialog shows up automatically in some situation (like restoring settings). This helps the user to avoid “forgetting” collections on the server.
    • Bug #10971 Auto-restore published shares
    • Bug #11334 Sync Menu items
  • Support and build for Mac OS X Leopard, Ubuntu Gutsy Gibbon and Use System Libraries: Modern OSes are now catching up with Chandler’s use of cutting edge releases of Python. So the good news is that, for those systems, we don’t have to bundle all these, resulting in much smaller downloads. We now provide special downloads for those Systems.
    • Bug #11088 Use system python on Mac (Leopard), Ubuntu Feisty and forward
  • Automate Upgrade Process: User now have the option to let Chandler export a .chex on quit. This is convenient for new users (small data base) with fast machines. For old timers with thousands of items, there’s an option to bypass this (don’t forget to export though _before_ upgrading to a new version of Chandler):
    • Bug #11139 Automate upgrade process

For a more complete list of bug fixes and known issues, please visit our Release Notes.

Thanks for your interest in Chandler Desktop!


What is Chandler supposed to be for, anyway?

December 5th, 2007 at 5:13 pm (5 months ago) by Mimi Yin under Product Design

We’ve heard from many corners that starting up Chandler is an intimidating experience, the app feels heavy, over-bloated with features. It’s taken me a long time to ‘get’ what that means. Here’s one explanation: (As usual, it has to do with context and history.)

When Chandler began, it was going to be the alpha and the omega of information management. It was going to swallow traditional PIM functionality wholesale (Email, Notes, Tasks, Calendar, Contacts) and extend to manage non-PIM data as well: Documents, Media, URLs, etc.

The theory was: The reason why information management sucks is due to a lack of integration. Integration in terms of data types and integrations in terms of workflow.

In the meantime, the world around us changed. Instead of a trend towards more ‘integrated’ solutions, people are adopting a wider range of tools and workflows are knit together via a wide variety of interoperation techniques.

What does this mean for Chandler? Do we still have a place in this new world?

I think so. I think we’ve actually been evolving with the rest of the world. We have not been working in a vacuum for the last 2 years. Instead, we’ve dramatically re-framed the way in which Chandler integrates. Chandler is no longer about replacing your email client, enterprise email, calendaring and content management systems, wiki, project manager, IM, news reader…

Instead, Chandler is meant to live in the middle of all these tools as a way to pull all the disparate bits and pieces of information we receive out-of-context, into a contextualized, personal and shared ’source of truth’.

That being said, the user interface we have today is misleading. It contains vestiges of the ‘old’ way of thinking about integration which has the potential to scare new users away, both because there is provokes a gut-level sense that the app is big and complicated and that you can’t get started without moving your entire world into Chandler.

For example, there is an out-sized emphasis on email functionality, left over from the days when we were adamant about being a complete PIM solution. In reality, email in Chandler today plays an important, but supporting role. We talk about it as a means of:

1. Outreach: A way to get information out of the ‘Chandler’ eco-system into other people’s Inboxes; and as a

2. Bridge: A way for Chandler users to get information from their email clients into Chandler.

So, how do we proceed to lighten-up the app so that it’s a more accurate reflection of what Chandler is meant to do? Here are some ideas:

  1. Remove the Reply, Reply All, Forward buttons from the Toolbar; and

  2. Add a Reply/Forward menu item to the Item menu

  3. Remove the the ‘New’ button from the Toolbar and really focus on the quick item entry bar as the way to create new items in Chandler.

  4. Rename the Mail application area Messages so that it’s more of a ‘Message Center’, a place where you can see the messages you sent/received from Chandler (not un-like Inboxes for social networking sites like Facebook or Linked In), and less of a “Mail Application”.

I will be thinking about this in the coming weeks and am interested in other perspectives. See discussion on the list: http://lists.osafoundation.org/pipermail/design/2007-December/008035.html


Chandler Server (Cosmo) 0.10 released

December 3rd, 2007 at 2:08 pm (5 months, 1 week ago) by Ted Leung under Chandler Server Development

The Chandler Project is pleased to announce the 0.10 release of Chandler Server (Cosmo)!

Chandler Server is a server and Ajax web UI for managing and sharing calendars, events, and tasks. It implements open data standards including CalDAV, WebDAV, Atom, and Atompub.

This is a bugfix release for Chandler Server 0.9 and is recommended for general usage. Important bug fixes address iCal3 interop, bugs in overlays, and some usability improvements in the signup workflow. Chandler Server 0.10 is currently available for download as a ready-to-run bundle at:

     chandlerproject.org/serverdownload

and the source code is available from subversion at:

     svn.osafoundation.org/server/cosmo/tags/rel_0.10.0

Send us feedback at the open mailing list:

     chandler-users at osafoundation.org

We look forward to hearing from you!

The bugs fixed in this release are:

8351 Cosmo time out on Firefox 1.5
8720 Sign up for an account + adding the currently viewed collection
8890 User action for resend activation email
10285 Account Browser: download as iCalendar yields 3 js errors
10904 Update Cosmo Olson files
11079 Can’t create Hub account with 20-char password
11080 Sharing error on my PersonalAK collection on Hub
11114 Cosmo doesn’t allow titles longer than 256 characters
11118 Feed service way to put an item in multiple collections
11133 Event missing EIM EventRecord
11138 QA needs JS hooks for he next/previous buttons in the dashboard
11144 iCal3 Interop :: Events stamped as tasks don’t show up as either in iCal3
11163 Collection creation in feed service
11250 invalid VALARM TRIGGER appearing in hub data
11282 NPE in triage status query
11467 bad xml attribute data causing ERRORs in hub log
11011 Write-up instructions on how to publish from other apps
11053 Include collection hue in EIMML
11142 iCal3 Interop :: Error when creating new collection from iCal3
11193 Use Dojo layered build functionality
11255 Collection overlay in IE 7 with multiple collections
11256 IE 6 collection overlay scroll bar overlaps the dashboard selector
11272 Non-selected, non-overlaid calendar lozenges showing
11292 invalid collection href on hub
11422 error during build - testEventStampValidation failed
11301 Collection deletion in feed service

A summary of known issues in this release is available:

     chandlerproject.org/knownissues

There was no change to the database schema for Chandler Server in version 0.10. Instructions for upgrading from previous versions of Chandler Server can be found at: <http://chandlerproject.org/ Developers/ServerBundleInstallation#Upgrading%20fromPMrevious%20versions>