Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!rutgers!aramis.rutgers.edu!athos.rutgers.edu!wiechman
From: wiechman@athos.rutgers.edu (NightMeower)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Getting started with Mac programming
Message-ID: 
Date: 26 Sep 89 13:20:35 GMT
References: <7893@leadsv.UUCP>
Distribution: na
Organization: Rutgers Univ., New Brunswick, N.J.
Lines: 29


Here's a vote for MacApp and OOP, and soon to be C++.  My first
program was written in an non-OOP and contains numerous bugs which
still haven't been tracked down.  After switching to MacApp, I'll
never go back.  It comes with many examples that demonstrate dialogs,
text editing, the important undo structure, and a solid but forgiving
library of routines.  Much of the information contained in IM 1-5 is
useful but can be gradually consumed rather than all at once with
MacApp since you need to only override things that you wish to change.
By gradually overridding things you can easily one thing at a time
leading to nice step-by-step refinement.  Each method has a clearly
defined purpose which gives you an idea of what it does plus with
"objectness" is easily reusable.

MacApp does have its drawbacks though.  You'll add quite a bit of size
to your final application but that can be made up for if you have many
similar actions.  MacApp is not designed for the next greatest selling
arcade game but is plenty fast enough for a word processor or
spreadsheet which need the undo function.

I am not an Apple employee so these comments are biased.


Kevin
-- 
===========================================================================
Kevin S. Wiechmann			arpa:  wiechman@rutgers.rutgers.edu

	 This is only a test... for the next sixty seconds...