Author Archive

Feeds: RSS | Atom

Thunderbird Plugin For Chandler

January 18th, 2008 at 4:28 pm (3 months, 3 weeks ago) by bkirsch under Chandler Desktop Development, Chandler Server Development, Product Design

Mimi and Katie talked in ealier posts about expanding the Chandler Universe by developing a Plug-in for Thunderbird.

The plug-in would allow Thunderbird users to interface directly with the Chandler Hub.

Some of the current ideas on what actions the Thunderbird Plug-In would perform are:

  1. Sync messages in IMAP Drafts/Sent folders with Chandler Drafts/Sent messages.
  2. Stamp a message and add it to a list of collection(s)
  3. Assign Triage status to message items
  4. Map individual IMAP folders to collections
  5. Receive notifications from Hub Service when: a. New / Edited items in a collection b. Items tickled to NOW

What features would others like to see?

Is the idea of a plug-in to Thunderbird useful to the Chandler User base? Will a plug-in help attract new users?

If you have any suggestions for features that you would like to see implemented in a Thunderbird plug-in now is the perfect time to share them.


Brian’s EuroPython Wrap up!

July 24th, 2007 at 4:41 pm (9 months, 3 weeks ago) by bkirsch under Chandler Desktop Development, OSAF, Public Events

Well I just got back from EuroPython 2007 held in Vilnius, Lithuania.

EuroPython was definitely smaller than our American Pycon counterpart and the diversity of talks more limited.

My favorite talk was on Streaming with Python, Twisted, and GStreamer.

I particularly enjoyed meeting developers on that side of the hemisphere who don’t normal make it to the American conferences. Overall, EuroPython had a very intimate feel.

On July 10th, I gave a lightening talk on Chandler which went very well.

I was trying to figure out how to capture all the functionality of Chandler in 5 minutes or less of speech time. I decided to run our Functional Test Framework while describing the different features Chandler has as the suite was creating new collections, new items, stamping, configuring accounts, sending email, publishing collections, and subscribing to collections. All in all I was able to show a large amount of Chandler functionality this way in under 3 minutes.

I then quit the tests and switch to a running version of Chandler spending the last two minutes demonstrating how internationalization and the plug-in framework work in Chandler. Specifically, I did an Amazon search for Scott Rosenberg and showed the collection results as well as an EVDB search for Opera in San Francisco.

I got a very good reception from the audience. As many people had not been following Chandler in a while they were surprised at how much recent progress had been made.

On July 11th, I gave my Internationalizing in Python: Chandler a case study presentation. It went very well also. There was strong turn out and I think may people were surprised out how hard it is to actually Internationalize / localize an application in Python.

In addition to showing slides I gave code examples of EggTranslations, PyICU, and how to create localization eggs using the Chandler tools.

You can view photos from the conference as well as access my presentation slides at:

http://people.osafoundation.org/bkirsch/europython/

On July 12th and 13th I hosted two days of Sprints on localizing Chandler.

I must say I learned a great deal. One thing that I had not considered is that localizers also make a very good focus group on Chandler usability. Since none of the translators had worked in depth with Chandler before, it was not only an exercise in how easy is the application to localize but also how easy is it for someone to start Chandler and grasp the concepts the application offers.

There were many issued raised at the Sprint including bugs in the Chandler code that are hindering a complete localization, better tools that need to be provided for localization, and ways that we need to better organize our strings in code to create a usable Chandler.pot for translators to work with.

I would classify those two days as providing the last few missing pieces regarding Chandler’s localization strategy.

I am excited to get started on providing the user community with the ability to localize Chandler in our 0.7.1 release which will follow Preview.

I have summarized the entire experience of the Sprints and next steps for Chandler i18n / l10n as well as included a link to the Swedish translation egg created during the Sprints here:

http://people.osafoundation.org/bkirsch/postsprint/

-Brian Kirsch


Internationalization on the way

June 13th, 2005 at 11:18 am (2 years, 11 months ago) by bkirsch under Chandler Desktop Development

One of the major lessons we have learned from other software projects is: design your product from the beginning to be localizable. Many projects that failed to consider Internationalization concerns in the architecture discovered just how hard it is to bolt on at a later date.

In the next few days I will be publshing the second version of the Chandler Internationalization Proposal. To give you a sneak peak, Chandler will be leveraging IBM’s ICU library and porting it to Python via Swig wrappers and will be adding new types to the Repository to support Localization of Unicode text. We will also be writting a custom version of pygettext.py that lets developers use the gettext .po format that is industry standard in the Open Source community while leveraging the Repository for the storage of translatable content.

Stay tuned!