the Dashboard purely as a place to collect new notes, an “intake” area
collections must be initially kept out of the Dashboard
everything that could possibly be worked on right now needs to be in one place. I use the Dashboard to answer the question, ‘what should I work on next’. Every Collection is in the Dashboard
Without paying attention to database technologies, the easiest comparison might be with iTunes.
Concerning the Save command, in the File menu: iTunes has no need for this, the application simply works. To users, the absence of a Save command is unremarkable.
no apparent rhyme or reason for the way in which sub-folders and sub-sub-folders are arrayed, making it difficult for you to predict as you navigate through each level of the hierarchy, what sub-levels will appear. It also makes the hierarchy as a whole, difficult to grok once you opened up a few branches of the hierarchy. You're presented with an array of relationships and no easy way to chunk them down
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
I wish to offer feedback and suggestions relating to design/UI of Chandler Hub and Chandler Desktop.
To me, it's not clear which of the two lists - chandler-users or chandler-dev - should be addressed.