🚀 go-pugleaf

In article <1312@utastro.UUCP> fritz@utastro.UUCP (Fritz Benedict) writes:
>...Kill DAs
>	Stars 1.1
As the author of Stars, I assure you that Stars 1.3 works fine on my
DataFrame 20, but please, please, everybody use the current version of my
stuff, if you're going to use my stuff at all.  I work hard to get the
bugs out before I post, and I try to be responsive to bug reports - I have
to, I have nightmares about people losing work because of my bugs.
If the current version still gives problems, let me know the symptoms.
(once again, I've had no problems.) I will either fix the problem and
broadcast to the net, or publically warn people away from my software.
And like you, I've got too much pride in my work and my skills to take
that latter step lightly.

In answer to Peter Korn:
  Although Stars does write directly to screen memory, I use the Apple
aproved method of finding out where screen memory is.  For example, Stars
works just fine on a Mac XL, which not only has the screen in a different
place, it also has a different shaped screen!

  I use Menu Clock instead of JClock (no surprise, I wrote Menu Clock over
a year ago.) the current version is version 2.1, and it quite solid.  It
is even compatible with Stars, something JClock is not.

  Killer DAs: some applications don't call ALL the Mac's Init... routines.
For example, a graphics program might not call TEInit();  Now, suppose you
bring up a DA like MockWrite, that uses TextEdit.  It must assume that
TextEdit was initialized by the application, it would be an error to call
TEInit() a second time.  Result: the desk accessory gets a bad rep, but it
was the application's fault.
--- David Phillip Oster		-- "The goal of Computer Science is to
Arpa: oster@lapis.berkeley.edu  -- build something that will last at
Uucp: ucbvax!ucblapis!oster     -- least until we've finished building it."