Hi folks, I've been overwhelmed by all the messages and discussion here, so I can't claim I've read a significant amount of the messages in this list. However, I thought I'd add a bit of trivia and a suggestion, and play devil's advocate:
There has been a similar process like the one that led to E-Mail-Init back when HyperCard was canceled. The OpenCard/FreeCard project. We had a mailing list, lots of ideas, lots of potential users, a generous and smart project lead... I'm sure most of you have never heard of FreeCard, it never got anywhere. What's left of that project and a second attempt, Project XI, can be found at <http://www.creysoft.com/xtalk/>. So, what I think is, why not start with the foundation? What Letters.app will definitely need are the basics: Some classes that speak the IMAP protocol correctly and expose messages, servers, mailboxes etc. as low-level data types, and a MIME decoder/encoder that can extract/attach attachments, find out if something is an HTML E-Mail etc. No matter what decisions are made for the UI, you will need this, and the design will be the same. Should everything go wrong, and Letters.app fail, the least the community will get out of this is the foundation for an open-source e-mail client. Anyone picking up afterwards will be able to do whatever UI they want on top of an already-established IMAP client core. If someone disagrees with the UI decisions made for Letters.app, there will be a common, shared core to build on, and everyone can create the special UI that fits their needs. Thoughts? Cheers, -- Uli Kusterer "The Witnesses of TeachText are everywhere..." http://www.zathras.de _______________________________________________ [email protected] mailing list List help: http://lists.ranchero.com/listinfo.cgi/email-init-ranchero.com
