Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!wuarchive!sdd.hp.com!elroy.jpl.nasa.gov!ncar!asuvax!stjhmc!p88.f15.n300.z1.fidonet.org!Lawson.English
From: Lawson.English@p88.f15.n300.z1.fidonet.org (Lawson English)
Newsgroups: comp.sys.mac.programmer
Subject: MacApp examples Was: Local/AppleTalk Connectivity in MacApp
Message-ID: <34241.27875335@stjhmc.fidonet.org>
Date: 5 Jan 91 18:33:19 GMT
Sender: ufgate@stjhmc.fidonet.org (newsout1.26)
Organization: FidoNet node 1:300/15.88 - Tucson Apple Core, Tucson AZ
Lines: 23

Kent Sandvik writes in a message to All

KS> That's exactly the current trend with application frameworks. 
KS> Isolate and connect at few places - sort of data abstraction 
KS> in the class level. The perfect case is where you could develope 
KS> the user interface separately from the the application grunt 
KS> class hierarchy, and attach these together as the last step. 

It should not be necessary for the Application/document classes to know about
everything: why should they? If they know about a class, and THAT class knows
about some class that it uses, the interface for the second class need not specify
a subclass, merely the parent (hopefully something already in MacAPP), THEN
the implementation section of the second class should use  the Unit of the sub-class
and typecast the parent class var to the sub-class. This speeds up compile times
by a factor of 2 or more.


Lawson
 

--  
Uucp: ...{gatech,ames,rutgers}!ncar!asuvax!stjhmc!300!15.88!Lawson.English
Internet: Lawson.English@p88.f15.n300.z1.fidonet.org