ric@islenet.UUCP (Frederick Lee) (12/21/87)
Flame ON! It would be better for us if Apple formatted their technical notes on CompuServe and elsewhere on a less-esoteric format than MacDraw. Perhaps in MacPaint so that those of us who have FullPaint or SuperPaint, etc. could gain some helpful information without the need of another costly software. Such illustrations would be better displayed and enjoyed by more Mac users. Flame OFF!
denbeste@bgsuvax.UUCP (William C. DenBesten) (12/23/87)
From article <3706@islenet.UUCP>, by ric@islenet.UUCP (Frederick Lee): > Flame ON! > It would be better for us if Apple formatted their technical notes > on CompuServe and elsewhere on a less-esoteric format than MacDraw. > > Perhaps in MacPaint so that those of us who have FullPaint or SuperPaint, > etc. could gain some helpful information without the need of another costly > software. > > Such illustrations would be better displayed and enjoyed by more Mac > users. > > Flame OFF! MacDraw is not an "esoteric" format. As I recall, it was one of the programs that Apple released very early on in the life of the mac. I remember that the first mac that I saw had MacWrite, MacPaint, and MacDraw. The reason that Apple uses MacDraw rather than MacPaint is twofold. 1) The pictures contain text that is too small for MacPaint to do a reasonable job of displaying. 2) MacDraw is capable of taking full advantage of the LaserWriter and making very pretty pictures. If you can gain access to MacDraw for a little while, you could use it to convert the files from DRWG format to PICT format, that SuperPaint is capable of reading them. You could even try cutting it from MacDraw and paste it into MacWrite or MacPaint. (I suspect that the picture is too large for MacWrite, and MacPaint would look pathetic.) --- William C. DenBesten | CSNET denbeste@research1.bgsu.edu Dept of Computer Science | UUCP ...!cbosgd!osu-cis!bgsuvax!denbeste Bowling Green State University | Bowling Green, OH 43403-0214 |
pollock@usfvax2.UUCP (Wayne Pollock) (12/24/87)
Regarding tech note #164, I have two relavent stories:
1) When I moved to Ohio, a friend was showing me around. Turning down a
certain street he said "now you'll see an example of mid-western road
repair." Around the next bend was a sign saying "Dip in road."
2) When I discovered some problems in an IBM product once, I reported it and
received an interesting (and now, famous) reply: "Its not a bug, its a
feature!"
I'm not sure which story is more appropriate to this tech note, but I am sure
that I am very disappointed by the attitude this shows!
I don't care that the code will somehow work even if certain functions and
variables aren't declared explicitly. Good software design dictates that
all objects be declared, especially in system software. This is necessary
for portability (both imported software, and improved "macs of the future")
as well as debugging; Assuming something is an int because you can't find
a declaration is not the way I like to work!
A tech note that says "here's a bug we won't fix" (story #1), or that says
"its not a bug, its a feature" (story #2) is not particularly useful.
Obviously, people are complaining to you about this. How 'bout a real
answer?
Wayne Pollock, The MAD Scientist
E-MAIL (Usenet): ...!{ihnp4, cbatt}!codas!usfvax2!pollock
(GEnie): W.POLLOCKcnc@hpcilzb.HP.COM (Chris Christensen) (12/25/87)
>If you can gain access to MacDraw for a little while, you could use it >to convert the files from DRWG format to PICT format, that SuperPaint >is capable of reading them. There are conversion programs in the public domain that will do this. The BMUG Graphics 1 disk contains more conversion programs to various formats than I have ever needed. cnc