The number and nature of the special explanations, criteria and limitations of e-mail in Chandler Desktop make me think that 'Email' its sub-headings, as currently presented in 'Get Started', should not appear in Get Started.
I suggest leaving references, from the Get Started page, to pages that are dedicated to: (1) an overview of e-mail in Chandler Hub and Chandler Desktop, and of limited communications with IMAP and POP servers; (2) using Chandler Desktop to configure an IMAP server, and understanding the workflows (in particular, the aspects that are one-way, periodic (Chandler Desktop sync) and incremental (the effect of adding messages to a Chandler-specific mailbox that was previously synced)); (3) e-mail in Chandler Hub; (4) e-mail in Chandler Deskop.
Critically: the overview should contain no instructions on use; it should present, in pictures and in few words as possible, the current workflow and vision, plus maybe no more than one vision of the future.
I see no requirement for IMAP client and Chandler Desktop to be on the same computer.
IMAP client at computer A communicates a user-initiated move of a message to one of three Chandler Desktop-specific IMAP mailboxes.
Chandler Desktop at computer B performs a one-time download from those three mailboxes.
early adopter, metrotechnicals as experimental email users
One-time download of new mail from IMAP
Basic message composition
Required features for supporting collaboration workflows
Reply, reply all, forward
Send and receive
rich text editing
draft, queued, sent, read, unread, needs reply, replied to, forwarded
email status column
Email threading support
overall clustering solution
stamping communications workflows
Features not targeted for 1.0
Drag and drop emails and attachments from other email clients
The OSAF vision of Chandler originated around 2001. In 2007: the preview milestone version was certainly (but not disappointingly) some way away from the release. Chandler 1.0 was released in August 2008.
unusual projects supported through the Foundation’s program in Research in Information Technology, Chandler
developed by the Open Source Applications Foundation (OSAF), led by Mitch Kapor, and over the next two years OSAF will receive a total of $2.75 million to develop
A most remarkable omission from the reviews on Amazon (and presumably, from the book) is: discussion of standards, such as those relating to CalDAV.
OSAF/Chandler Project members made significant contributions to the drafting and setting of standards.
Happily, we don't hear companies such as Apple or Google criticising Chandler Project history whilst embracing/enjoying CalDAV. I suspect that - however well written the book may be - a *focus* on a space in time (however short or long) has overlooked the broader value of the Project.
"Our civilization runs on software. Yet the art of creating it continues to be a dark mystery, even to the experts, and the greater our ambitions, the more spectacularly we seem to fail. … [this book] sets out to understand why, through the story of one software project -- Mitch Kapor's Chandler, an ambitious, open-source effort…
continue to support items
in multiple collections in a first class way on the server, which in
turn means that the web UI and future web widgets will handle this
case elegantly as well :D