Philippe Bossut wrote: > However, in the course of this thread, it seems that we are now assuming > that some UI is required in the email client...
The UI I've been talking about definitely not about email-client UI. The proposal supports integration with every email client and server available. For UI, we need a way for someone to optionally pick the email address that will become "live" as a way to submit items. That's probably an additional field on the Chandler publish dialog. For what it's worth, I completely see how this option helps bridge the gap for me and others. If I publish an email address for my primary collection(s), then I can use the "forward" mechanism of my client(s) to enter items into Chandler. Moreover, I can also use my server-side and client-side filters to auto-submit certain kinds of items that enter my world via email (1200 a day at last averaging) straight into Chandler. > 1- keep the address/subject scheme very simple so that users can do it > themselves (i.e. forward to their calendar address and doctor the > subject line by hand) That's the current consensus proposal that Mimi and I have both endorsed. -- Jared _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
