Developer's tour of Chandler Next Generation PIM. Focus on making a basic project which is highly reusable and growable. Calendar is not that far away. Counting in Months, not years. Reminder of the BOF Ted Leung Focussed on the repository portion of the architecture Not just building an app, but a substrate to allow other items to access data. WxWidgets as portion of GUI. WxPython binding to that. Chandler repo is next to such. Built on SleepyCat, DbXML, pyLucene. Query runs across all layers. Extensibility provided by Parcels - and a parcel loader. Secoond layer providing services for parcels - twistedPython, a scheduler manager (app scheduling). Notification manager for interparcel comm. Content Model - 'schema' definition for items (email, task, appt). WebDAV as a tactical choice. Chandler Repo Item Based data bidirectional Integrated w/Python Schema described by XML Supports concurrency and threading, Full Text indexed (pyLucene). Compiled Java Lucene with Python wrapper. Services Layer Standards (IMAP/POP WebDAV XMPP CALDAV (http://xml.coverpages.org/ni2003-12-31-a.html) CVS, wiki (RSS) Mailing lists IRC, etc Roadmap 0.4 in Oct 2004 (Experimentally usable, calendar) 0.5 3-5 months subsequently (basic end user usage, etc) 1.0 'in 2004' John Anderson on CPIA (Presentation and Interaction Architecture) Kappor, Anderson, Hertzfeld Thre primary goals Chandler specific UI building Blocks (fully conversant with Chandler types) Blocks independent of presentation platform Enable 'non-programmer' build mode. More fully baked blocks than most toolkits Blocks intercommunicate. 'Chandler Events' Block Types Container Blocks Tree. List blocks Compound Blocks Email - Brian Kirsch Items become multiply referecneable and viewable First problem - what libraries? IMAP Library, Mail Parsing Library. Chose Twisted for former (and SMTO) Discussion of GtD integration.