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: <47800@apple.Apple.COM>
Date: 6 Jan 91 22:14:08 GMT
References: <14545@hoptoad.uucp> <47760@apple.Apple.COM> <14582@hoptoad.uucp>
Organization: Apple Computer Inc., Cupertino, CA
Lines: 33

In article <14582@hoptoad.uucp> tim@hoptoad.UUCP (Tim Maroney) writes:
>In article <47760@apple.Apple.COM> ksand@Apple.COM (Kent Sandvik) writes:
>>That's exactly the current trend with application frameworks. Isolate
>>and connect at few places - sort of data abstraction in the class
>>level.

>I'm glad to know that I'm in tune with the latest thinking.  I do wish,
>however, that some attempt had been made to communicate this thinking
>together with the class library, instead of forcing me to discover it
>myself.

>Not only did I have to figure it out rather painfully over a period of
>months, I had to contest with a fellow programmer who learned MacApp
>from Apple's course and the example programs, who would always say,
>"But look, in the example programs this is how the units are connected;
>that's how Apple wants you to do it."

Well, I learned this OOPS strategy at an Apple MacApp training course :-).

>Please, let's get some examples that reflect a good class style.

Anyway, good constructive criticism is always healthy, I will discuss this
with other DTS engineers concerning future MacApp example source code.

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