Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!apple!ksand
From: ksand@Apple.COM (Kent Sandvik)
Newsgroups: comp.sys.mac.programmer
Subject: Re: OOP--What do you think?
Message-ID: <52134@apple.Apple.COM>
Date: 28 Apr 91 23:51:05 GMT
References: <0B010004.difjcc3@outpost.UUCP> <1991Apr29.092809.323@otago.ac.nz>
Organization: Apple Computer Inc., Cupertino, CA
Lines: 39

In article <1991Apr29.092809.323@otago.ac.nz> michael@otago.ac.nz writes:

>My main problem is that the documentation is just inadequate when I want to
>find the answer to a given question, and I usually can't even figure out
>whether or not the question is inappropriate. What I really need is a guide to
>each object type which would describe its fields and methods and *what they are
>intended to do*. This is what is so often missing from the present
>documentation and frequently forces me to read the MacApp source. This should
>not be necessary. Then there are other things that just aren't there; try
>finding a description of how to segment your application in the 2.0.1
>documentation...

True, this is a valid comment. MacBrowse (or 'Mouser does-something' for us
initiates) is one way to establish relationship information between
classes. For instance the function of flattening classes, i.e. find
out all the instances where a certain method is called, is very useful.

The combination of MacBrowse and 411 (inside MacBrowse) will help
to a certain degree the problem with finding relationships in large
object frameworks.

I once answered a DTS question about how to name segments with MacApp code,
it will become one of the standard answers in our DTS Q&A stack (if it's
not there already). If I find it somewhere on my hard disk I will post
it, but true, stuff like this should be better documented. 

The DTS Q&A stack, as well as the new Developer Tech Support Library
on AppleLink is one way to fill in the gaps in the common documentation.
Tech Notes that we produce is also one way to provide additional information. 
We have a couple of tech notes about MacApp - I will look into the
issue how to streamline the tech notes and maybe provide a better
framework for MacApp tech notes in future (instead of having x amount
tech notes to check every time).

Regards,
Kent Sandvik, DTS

-- 
Disclaimer: Private and personal activities on USENET, non-company sponsored