From: rpomeroy@aunext3.cam.amd.com (Ron Pomeroy x(Coop))
Newsgroups: comp.sys.next.programmer
Subject: Re: Reuse in Nextstep
Date: 31 Aug 92 14:10:15 GMT
Reply-To: rpomeroy@aunext3.cam.amd.com
Distribution: usa
Organization: Advanced Micro Devices, Inc.; Austin, Texas

In article <1992Aug28.033732.2031@corndog.id.com> walters@id.com (Chris  
Walters) writes:
>>In article <1992Aug25.133146.21009@monu6.cc.monash.edu.au>  
>>ede978e@monu6.cc.monash.edu.au (Robert D. Nicholson) writes:
>>> I'm studying how Reuse is implemented in NextStep
>>> specifically how one can strucutre an application such
>>> that the represenation of the view/interface is
>>> competely indepentent of the application's
>>> functionality.  For instance if an application wished to
>>> switch its interface from graphical to text or vice versa
>>> or both how one would structure this using NeXTStep and
>>> Interface Builder, it seems that most applications are
>>> tied directly into interface builder.  ie. the
>>> functional component of the code messages IB outlets to
>>> maintain application state.  Has anybody every designed
>>> something that was totally separate from IB?  If so Id like
>>> to hear about it.
>>> 
>>
>>Well, I think kits like the Indexing Kit and the DBKit
>>(or at least parts of it) are beautiful examples of reuse
>>in the appkit which is independent of the UI.  There 
>>are loads of others.
>>
>>With the addition of protocols in 3.0 Objective-C, we 
>>now have tools which greatly facilitate the reuse of 
>>_interface_, versus the reuse of implementation.
>>
>>From the release notes, (without permission:)
>>
>>"Protocols allow you to organize related method into
>>groups that form high-level behaviors. This gives
>>library builders a tool to identifiy sets of standard
>>protocols, independent of the class hierarchy.
>>Protocols provide language support for the reuse of
>>design (i.e. interface), whereas classes support the
>>reuse of code (i.e. implementation). Well designed
>>protocols can help users of an application framework
>>when learning or designing new classes."
>>
>>However, one reason (IMHO) that apps tie in tightly
>>with InterfaceBuilder is because it is so easy to
>>do.  Designing for reuse it not always the primary
>>goal when building an application (ever heard of
>>rabid prototyping? :-)
>>-- 
>>Chris Walters			10600 Arrowhead Dr., Suite 350
>>RDR, Inc.			Oakton, VA 22030
>>walters@rdr.com			(703)591-8713,(703)273-8170 FAX
>> ------------------------- Hack Naked --------------------------
                             ^^^^^^^^^^
				Naturally ! 

Huuuurrrrraaaaayyy. When I first used protocols in SmallTalk/ObjectWorks I  
didn't think much of them.  Now that I'm working on a big project, I find them  
really usefull (if not indispensible).  Waaayyyy kool NeXT :-)  Now,  do they  
show up in IB ? And, can I just "add protocol" as easily as I can subclass in  
IB ?

BTW - A sweet lady (whose name I will withhold) said 3.0 went to the press on  
the 25th.  She wouldn't comment on when customers would first start receiving  
their copies.  Oh well. 

--
Ronald Pomeroy (waiting for my 3.0)
Advanced Micro Devices
CAM Applications Group
rpomeroy@aunext3.amd.com