🚀 go-pugleaf

In article <Bv9G6t.I34@news.cso.uiuc.edu> jeffo@uiuc.edu (J.B. Nicholson-Owens) writes:
>Dave Griffiths writes
>> Interesting, but you guys are speaking another language.
>
>Actually, I don't think so.  What has been called a 'module' could be thought  
>of as a Kit of some sort.  One that provides the added functionality already  
>spoken about.  All the functionality that needs to be shared could be bundled  
>together inside a MailKit.
>
>> For those of us still waiting for 3.0, what are these "modules" you're
>> talking about? 
>
>They don't exist now, but to make it easy for other apps to take advantage of  
>them ('them' being the features listed before this post) it would be  
>advantageous to make them independant of any one app in particular.
>
>> Are you sure that NG and Mail both use them? 
>
>You've obviously not been following this thread.  I will elaborate.

Thank you for explaining. I _had_ been following this thread, and in the
context it sounded like Mike was suggesting making use of "modules" to
overcome shortcomings in Mail _now_. I assumed (or rather hoped) that 
"modules" were a fancy new feature of 3.0 that let you add functionality 
to an app.

>Upgrade the module, and both NG and Mail are  
>upgraded (plus whatever else uses that module).

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).

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.

Dave Griffiths