🚀 go-pugleaf

In article <3949@ece-csc.UUCP> jnh@ece-csc.UUCP (Joseph Nathan Hall) writes:
>Seriously, folks.  These are simple questions but unfortunately not stupid
>questions in the Mac programming world.  I find it immensely frustrating
>sometimes trying to discern the *simplest* things about the Toolbox and
>OS calls.  There isn't even a good description of what a complex, real-world
>event loop should look like in Apple's documentation.
>
>For example:  IM I has a TextEdit chapter.  But where does it say that
>lines in the TextEdit record are terminated in carriage returns?  (What
>should I assume?  Could be LFs, NULLs, whatever!)  Where does it say whether

some stuff deleted

>Furthermore, there should be GOOD examples of complex Pascal and C event
>loops available from Apple (in a book!)--something like a Macintosh
>Application Programmer's Guide.  Not piecemeal (Programming for Multifinder--
>yuck!), but a good, solid, systematic introduction to the event loop
>programming style, + common idiomatic techniques, readily available.  You

more stuff deleted

>But still ... what do we user/programmers have to do to get decent reference
>materials from Apple?  Why do we join APDA, collect inaccurate/
 
 Maybe some of us on the net can draft a book (article,letter
 or what ever you want to  call it) on the subject of 
beginning macintosh programming and call it "Everything that you wanted
to know about mac programming but were afraid to ask!". It could include
up-to-date info on the Mac and source code examples. some snippits from
the net about gotchas and bugs. That way if someone asks on the net about 
beginning programming on the mac we could just email them a copy.

just an Idea :-)
Matt Mora
SRI International