🚀 go-pugleaf

In article <3955@ece-csc.UUCP> jnh@ece-csc.UUCP (Joseph Nathan Hall) writes:
>In article <169@indri.primate.wisc.edu> bin@primate.wisc.edu writes:
>>
>>Of course, you have to be able to get source code, and since HARDLY
>>ANYONE POSTS ANY --- STILL!!! --- you may be out of luck.
>>
>
>I've heard from a few people since my last posting who seem to concur that
>the lack of *real* programming references is acute, and that there is not
>much of a consensus, additionally, as to how one should organize a Mac
>application internally, particularly the event loop.
>
>I'd like to suggest that we USENET-ters produce a "Mac Programming Guide."
>In particular, we should produce a document describing, in detail, a good,
>workable event loop with support for everything; in addition, we should come
>up with a collection of efficient paradigms for dialog handling, menu
>item dimming/hilighting, file save & load, text editing, etc.  Also, we should
>try to explore the general issue of event-driven programming as opposed to

Don't for get about the dirty word "scrolling".
I think it would be great to have a guide to get
a handle on the aspects of programming the mac. I remember
someone saying that before you can write you have to know
how to read. That goes for any language (be it english or 
any computer language). let's say you wanted to write a 
MDEF. You could scan the back issues of Mactutor to try to
find a good example (if you have all the volumes) only to find
that the author wrote it in a different language. Instead you
can pull out your trusty "Mac Programming Guide" look for the
chapter MDEF's and there you have it. Examples in of mdef's in 
C, Pascal, asm or whatever. Also at the end of the chapter will 
be a Gothcas and bug report.

Well I better stop my dreaming. (is it that close to april fools? :-))
Well if anyones counting  call this a yes vote.

Matt Mora
SRI International