🚀 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. 

After two years of playing/hacking at Mac Programming, we (my Mac specialist
and I) have a simple "blank" application in LSC which we could send off to
whomever is collecting the stuff (or even post [gasp!]) in comp.sources.mac
if the interest warrants it.  I handles a simple one window situation WITHOUT
controls, but it is fairly clear.  I know it could be better, and more
powerful, etc.  but we haven't the time to research everything and still get
the necessary programming done.  Let me know your feelings.
--
Greg Woodbury (using the account of Max Woodbury)
System Manager(UNIX) and System Programmer
Duke U. Center for Demographic Studies	(919)684 6126 (after 1pm EST)
US Mail: 2117 Campus Drive; Durham NC 27706 USA
UUCP: ...mcnc!ecsgate!dukeac!dukcds!ggw  or  ...duke!dukcds!ggw
Internet: ggw%dukcds@cs.duke.edu  or  ggw@dukeac.ac.duke.edu