The Chandler Project Blog

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

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

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

0.7.2 fixes over 80 bugs and includes some major improvements:

• Dashboard: Following up on users logged bugs and remarks, we improved the Dashboard display of the Who column and made it work more in sync with the other columns. We also changed how the triage status cycles. This fixes bugs:
  • Bug #10924 Chandler leaves the Who column blank when the user stamps an item but doesn’t address it
  • Bug #10925 Chandler displays ‘to’ if a message is neither fromMe nor toMe
  • Bug #10926 The order of Triage Status has been changed to NOW, LATER, DONE
  • Bug #10927 The ‘Edited/Updated by’ in the Who column is displayed only for unread messages
• Support for Ubuntu Gutsy Gibbon: We’re now using wxPython 2.8.6.0 which fixes crashes reported by several users of Ubuntu Gutsy Gibbon. This fixes Bug #10906.
• New version of PyLucene: Chandler’s PyLucene is not using gcj anymore, but rather our own home brew jcc. This fixes Bug #10803 among others.
• Auto fill for common email providers: Account settings now fill automatically for the most common email providers. Just type your email address and if the provider is recognized, most of the settings will be filled out automatically.
• Chandler-on-a-stick, a.k.a. “Portable Chandler”: Though not built automatically and available for download, it is now possible to build a relocatable distribution of Chandler that can be stored on, and run from a removable device such as a USB memory stick or an iPod.
• Getting ready for l10n (localization): Chandler Desktop 0.7.2 is not completely ready for localizers yet (still a handful of bugs to fix; this will happen in 0.7.3) but we solved a significant set of issues that will make the localization process much easier:
  • Bug #3740 Tests are now run on a Tinderbox using a non-ascii locale / charset for path
  • Bug #5658 Localized UI meta data stored in the Repository needs to be refreshable without altering User Data : There’s now a new language picker in the File menu making it easier to change language and test localization without having to throw the whole repository or use magic command line options
  • Bug #10132 Triage NOW, LATER, DONE images un-localizable : now those bitmaps are computed within Chandler using provided localized text. No more bitmaps to localize!
  • Bug #10136 Improving Chandler gettext tools
  • Bug #10139 Add context comments to Chandler Code. Extra L10N comments that display in po editors (like poedit) have been incorporated in the code to give context to localizers.
  • Bug #10140 Clean up the Python code to produce a more useable Chandler.pot : Chandler 0.7.2 does not use the English language translation file to correct inconsistency in the Python code so localization files can now be tested.
  • Bug #10957 Send button clips off screen when button label verbiage expanded
  • Bug #11061 Incorrect detection of country code on Mac OS X
  • Bug #11066 Can’t create events with international date formats
  • Bug #11073 The Application.restart method needs to shutdown all Chandler services
  • Bug #11106 Splash Screen needs to handle text expansion
  • Bug #11107 File Menu Item New ->New revisisted
  • Bug #11117 Rework the conflict resolution strings to be clearer to localizers
  • Bug #11135 Improve i18n of recurrence strings in emails
  • Bug #11162 Fix some missing mnemonics

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

Thanks for your interest in Chandler Desktop!

This entry was posted on Wednesday, November 14th, 2007 at 1:30 pm and is filed under Chandler Product News. You can follow any responses to this entry through the RSS 2.0 feed. You can skip to the end and leave a response. Pinging is currently not allowed.