Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!clyde.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!apple!ksand
From: ksand@Apple.COM (Kent Sandvik)
Newsgroups: comp.sys.mac.programmer
Subject: Re: MacApp examples Was: Local/AppleTalk Connectivity in MacApp
Message-ID: <47801@apple.Apple.COM>
Date: 6 Jan 91 22:29:04 GMT
References: <34241.27875335@stjhmc.fidonet.org>
Organization: Apple Computer Inc., Cupertino, CA
Lines: 47

In article <34241.27875335@stjhmc.fidonet.org> Lawson.English@p88.f15.n300.z1.fidonet.org (Lawson English) writes:
>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

The original thread in this discussion was why MacApp sample code does
not make use of isolated application class libraries. I assume that the 
comment above is just a 'yes-it-is-bad' comment. I tried to find some
kind of a statement that contradicts the earlier comments, alas did 
not find anything.

To continue with this discussion, Object Design is a fairly new area
to explore, and as long as we try to explore new methodogies the whole field
will evolve. As long as we lock ourselves to old, proven methologies we will
have a stagnation in the evolution of Object oriented systems.

I'm sure that there will be more exploration with states inside frameworks,
persistancy and other exotic aspects that only a few dares to test today,
and they will be 'common sense' in five years time.

Maybe some parts of MacAapp today seems to be wrong, but at least someone
tried to create the first workable framework in the first place. And 
as anything else, MacApp and MacApp application design is still evolving.

Regards,
Kent Sandvik

 
-- 
Kent Sandvik, Apple Computer Inc, Developer Technical Support
NET:ksand@apple.com, AppleLink: KSAND  DISCLAIMER: Private mumbo-jumbo
Zippy++ says: "C++, anything less is BCPL..."