🚀 go-pugleaf

Dave Griffiths writes
> [...] in the context it sounded like Mike was suggesting making use of
> "modules" to overcome shortcomings in Mail _now_. 

Actually, if someone is willing to do the programming on this, this wouldn't be  
bad.  Perhaps someone at NeXT would be willing to update Mail.app (yeah,  
right...) that used this, the MailKit could be distributed with it.

> I assumed (or rather hoped) that  "modules" were a fancy new feature of
> 3.0 that let you add functionality  to an app. 

I don't know about this.  There might be something that functions like this,  
but as of right now, to my knowledge, there is nothing.

> Now I'm probably being stupid again, but if this module or kit was
> supplied by NeXT then it couldn't be upgraded by a user could it? (Be
> nice if it could).

(It sure would be nice), but I agree.  Based on NeXT's releasing of source to  
the other Kits, I doubt that if NeXT made such a thing they'd release the  
source.  On the other hand, would they be willing to accept something that was  
freely available (under the GNU license) and include it with standard  
disribution?  It could only HELP apps like NG and Mail.

> But if you're talking about some design goals for a third party Mail and
> News reader, then yes, it clearly makes sense to share functionality in a
> kit of some sort.

Yeah, that's what I was yakkin' about before, but now that I give it serious  
thought (in relation to it's ability to be used in more currently available  
apps than NG) I think it's a great idea, but one with little future.

Oh well....I guess, once again, it's up to the small developers to make  
something more useful than what NeXT sells.
-- 
-- Jeff (jeffo@uiuc.edu)
-- NeXTmail ok