Brainstorm first; define 1.0 later

[Steven Degutis]

On the note of plugins, I think using Distributed Objects for remote access would also be a really nice way to provide integration with other native Cocoa apps (without the remote apps having to jump through hoops by way of NSNotifications or AppleEvents directly or whatever). I've only seen DO used in Papaya.app for this purpose, but it works really well (and a lot of the problems with using DO seem to disappear when you use it for IPC instead of remote machine messaging).

-Steven

On Jan 16, 2010, at 3:45 PM, Gus Mueller wrote:

> On Jan 16, 2010, at 1:41 PM, Brent Simmons wrote:
> 
>> It's too soon to talk about the specifics of a 1.0 release -- let's first just brainstorm, then we'll have a pretty good idea of what people are looking for.
>> 
>> What are you looking for in an email client?
> 
> A good UI, and extensibility via plugins.  So it would have to have some sort of a defined plugin api for programmers to code against.  It's really hard to this for a 1.0- so I'd suggest it be marked as "experimental", but it would be nice to have.
> 
> It would be also nice, if there were a standard database / message store that it wasn't tied to too closely.  That way forks could happen, and maybe a new client would be able to read the database without any problems.  Or maybe even another process (python?) could be able to read/write to the message store.
> 
> -gus
> 
> --  
> 
> August 'Gus' Mueller
> Flying Meat Inc.
> http://flyingmeat.com/
> 
> _______________________________________________
> email-init at lists.ranchero.com mailing list
> List help: http://lists.ranchero.com/listinfo.cgi/email-init-ranchero.com