Xref: utzoo comp.sys.mac:51326 comp.sys.mac.programmer:13473
Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!samsung!usc!apple!portal!cup.portal.com!ts
From: ts@cup.portal.com (Tim W Smith)
Newsgroups: comp.sys.mac,comp.sys.mac.programmer
Subject: Re: Inside Macintosh: Will we ever see a revised, updated editi
Message-ID: <28272@cup.portal.com>
Date: 25 Mar 90 11:04:32 GMT
References: <14532@phoenix.Princeton.EDU> <28002@cup.portal.com>
  <14452@reed.UUCP>
Organization: The Portal System (TM)
Lines: 26

>>While part of this posting is meant as a joke, part of it is serious.
>>You can get quite far in an application with just IM-I.
>
>Unless, of course, you plan to do any memory management, basic file i/o,
>or printing... :-P

Yes, you will need to glance at IM-II.  Actually, if you are writting
in C, you can use calloc and cfree from whatever standard libraries
your development system uses, and the stdio library for you file I/O.

This is not as bad as at sounds, since these are things that are hidden
from the user, so your application would look like a real Mac application.

But in general, you are right.  I was being a little too restrictive
in suggesting only IM-I.

My main point was that you do not have to read all five volumes of IM,
( or six if they release a volume for the new machines ) in order to
program the thing.

Sure, there are some things you miss if you don't read them all, but you
can learn these after you've got the basics down.  So what if your first
Mac program doesn't have heirarchical pop-up menus, and doesn't draw in
2^24 colors?

						Tim Smith