The Chandler Architecture Pilot Project

This page contains some references and (at the moment) brief notes about the Post-Preview (0.7) Chandler Desktop Architecture Pilot Project, as proposed on chandler-dev:

• Architecture Pilot Project Proposal (Grant)

In short, the goal is to have a demoable version of Chandler by the end of December 2007, missing persistence, email and sharing, but having separated and fully tested domain, interaction and presentation layers.

Discussions leading up to the pilot project

The motivation behind rearchitecting can be found in the following threads:

• What is next for Chandler desktop? (Katie)
• The Great Architecture Discussion of 2007 (Grant)

These spun off a couple of related threads:

• desktop priorities (next steps for desktop) (Katie)
• Performance, Scalability (Katie)
• PPD’s Chandler desktop wish list (Mimi)

Questions/Issues from the October 16, 2007 Desktop Team Meeting

• Will we branch, or start from a clean svn repository?
• What is the strategy for merging in bug fixes/changes that come in as the pilot progresses?
• Will script recording be impacted? (e.g., it currently relies on Block names in some cases).
• What event loop will we be using? (wx's for now, and eventually a wx-enabled twisted reactor)
• Should keep an open dialog about progress, so we can avoid some of the pitfalls (e.g. wx-related ones) that we're run into in the past.

Upcoming Changes

This is an attempt to list some of the proposed upcoming changes in Chandler trunk that could impact the design of the prototype. Though we’re not going to be implementing these, we do want to take care not to “design ourselves into a corner” here.

Sorting in triage view

Who column

-- GrantBaillie - 19 Oct 2007