Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!unmvax!pprg.unm.edu!hc!lll-winken!uunet!ncrlnk!ncr-sd!hp-sdd!hplabs!hpfcdc!bayes
From: bayes@hpfcdc.HP.COM (Scott Bayes)
Newsgroups: comp.sys.mac.programmer
Subject: Re: The USENET Macintosh Programmer's Guide
Message-ID: <11550006@hpfcdc.HP.COM>
Date: 21 Mar 89 00:16:02 GMT
References: <3966@ece-csc.UUCP>
Organization: HP Ft. Collins, Co.
Lines: 23

>I vote for MacWrite as the common denominator.
>

I agree. Everything ever made (it seems) imports MacWrite. I've received 
MS-Word files I've just had to trash, 'cause they're in a version I don't
speak. I've never had that happen with MacWrite.

Also, I think plain text as the only option sux wind through a straw. So
many explanations require graphics for good understanding (that last sentence
could probably have used a hearty dose ;-) Make text-only available as an
alternative for the poor-of-spirit, or other underprivileged, but have
MacWrite as the main format.

>Other neat-o topics to cover:
>
>-how to talk to the serial port (e.g., a simple modem-dialing program)
>-an AppleTalk demo
>
>-Ted

Minimalist display updating. How do I do a fast update when I see an InvalRect?

Scott Bayes