Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ncar!tank!uwvax!puff!rt4.cs.wisc.edu!blochowi
From: blochowi@rt4.cs.wisc.edu (Jason Blochowiak)
Newsgroups: comp.sys.apple
Subject: Re: What doc do I need
Summary: Methinks that for Sys 5.0 programming, the new APW tools are needed
Keywords: APW, System Disk 5.0, resources
Message-ID: <3314@puff.cs.wisc.edu>
Date: 15 Oct 89 08:41:47 GMT
References: <8910141319.AA04595@trout.nosc.mil> <35655@apple.Apple.COM>
Sender: news@puff.cs.wisc.edu
Reply-To: blochowi@rt4.cs.wisc.edu (Jason Blochowiak)
Organization: U of Wisconsin CS Dept
Lines: 48

In article <35655@apple.Apple.COM> dlyons@Apple.COM (David Lyons) writes:
> lvirden@pro-tcc.UUCP (Larry Virden) writes:
>> [That he has such and such refs, and wants to know what else he needs...]

>From APDA, you want the GS/OS Reference and the Volume 3 of the Toolbox
>Reference (you can use 5.0 stuff with ORCA/C even if they haven't released
>updated interface files yet--it's straightforward to declare your own
>structures and toolbox functions, using the information in TB Ref 3, modeling
>your declarations after the ones in the existing .h files).

	I think that the new APW tools disks are a requirement for programming
under Sys 5.0. Also, the (yes, incomplete) new interface files will work with
Orca/C: Just copy all the files from CInclude into OrcaCDefs, and then change
the language to Orca/C, with whatever name you've given it (I changed it from
CC to ORCAC), as Orca/C will gag if you try to #include an APW C file. DON'T
just nuke the old OrcaCDefs folder, as there are some files in OrcaCDefs that
are different than in CInclude (there are also some that don't exist in
CInclude).

	Aside from the interface files, Rez is mightily useful when you want
to use resources :) I've not been impressed by the other tools on the disk,
though, as I've run into bugs in every one that I've used (with the exception
of DeRez). DiskCheck seems (I'm not sure if it was DiskCheck that mangled one
of my partitions - it might've been something else) to be particularly unsafe.

	They also finally got around to defining the macros that let you
define OS and tool structures with the assembler, although I'm not particularly
fond of the fact that they put ALL of them in one (>100k, I believe) file.
They also have 2/RInclude/Types.Rez, which contains the Rez type definitions
for ALL of the tools, etc. - this takes awhile to compile, even with a
TransWarp. Well, actually, the definition for PICTs is in another file, but
aside from that, they're all in one file.

	My, I never imagined I'd be plugging something that someone from Apple
forgot ;) (or perhaps didn't feel like mentioning at the time)

	One last thing - entering the definitions by hand, although cheaper
(in terms of cash going out the door), is significantly more error prone, which
can cause all sorts of nuisances. I #define'd one of the new bits for
TaskMaster that was forgotten in <window.h> incorrectly, and it took me a
long time to figure out what had gone wrong...

> --Dave Lyons, Apple Computer, Inc.          |   DAL Systems
--
                 Jason Blochowiak - back at school (again).
             blochowi@garfield.cs.wisc.edu or jason@madnix.UUCP

            "What's up pruneface?" - Bugs Bunny in the year 2000