Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84 (Fortune 01.1b1); site graffiti.UUCP Path: utzoo!linus!philabs!cmcl2!seismo!ut-sally!ut-ngp!shell!graffiti!peter From: peter@graffiti.UUCP (Peter da Silva) Newsgroups: net.micro.amiga Subject: Re: Request for mac sources Message-ID: <220@graffiti.UUCP> Date: Sat, 21-Sep-85 09:11:32 EDT Article-I.D.: graffiti.220 Posted: Sat Sep 21 09:11:32 1985 Date-Received: Wed, 25-Sep-85 09:29:06 EDT References: <251@h.cs.cmu.edu.ARPA> <6626@boring.UUCP> Organization: The Power Elite, Houston, TX Lines: 22 > Ha, ha, ha! device-dependent C for the Macintosh! Obviously you have not You mean device _in_dependant code, don'tcha? > seen many of the C sources that were posted to net.sources.mac (admittedly, > there weren't that many, but enoug to give one the taste). C code for the > Macintosh consists of about 5 % algorithms and 95 % toolbox interface, unless > you're writing HUGE applications. The typical demo program for instance > has four or five lines to draw a specific curve and the rest of the program > sets up windows, checks the keyboard and the mouse, and what-have-you. Which is really strange, since the dumb public-domain window package for the IBM-PC that I'm using just requires an openwin() and a couple of printwin() and plotwin()s to do the same thing. Maybe "everyone" should agree on a toolbox window environment & an interface for vanilla 'C' program usage. How many windows should you open to say "hello world"? Question on the Mac: is it possible to launch a program & hand it a window to do all it's text I/O in? Then you could just have a program that sets up the screen and so on & launches your hello-world program into it. I mean if the oh-so-terrible user-hostile AT&T PC7300 can do that, surely the super-friendly novice-chummy Mac can.