Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!fluke!mce
From: mce@tc.fluke.COM (Brian McElhinney)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Time for standard cmd-keys & menu c
Message-ID: <11538@fluke.COM>
Date: 5 Oct 89 23:14:20 GMT
References: <15720@dartvax.Dartmouth.EDU> <227700045@uxa.cso.uiuc.edu> <2062@ethz.UUCP> <253@dbase.UUCP> <15914@dartvax.Dartmouth.EDU>
Sender: news@tc.fluke.COM
Organization: Software of the Mist
Lines: 24

In article <15914@dartvax.Dartmouth.EDU> mjm@eleazar.dartmouth.edu (Michael McClennen) writes:
>
>It depends upon what you do for a living.  I write programs, and use a text
>editor that doesn't even have a style menu.  So I prefer command-P to be
>'Print' (what else would I use it for?)  If I wrote documentation with styles,
>or wrote prose for a living, I would probably want command-P to be 'Plain'.
>
>Isn't Resedit wonderful?

I assume you meant that in the spirit of ":-)" but, to be literal, hell no.
If you write documents for a living, you shouldn't have to touch something as
obscure, non-standard, and out-and-out *dangerous* as ResEdit.

Putting on my software management hat, the sheer number of revisions to
ResEdit makes me wonder if it should be thrown out.  As programmers, we often
get so attached to "our" code that we can't see the forest for the trees.
Starting the source code from scratch isn't as bad as it seems, since you
still have the knowledge that went into the original.  You usually end up with
a cleaner, more robust, maintainable, and extendible software package.  And
often faster than the *real* time reworking buggy code would take.
 
 
Brian McElhinney
mce@tc.fluke.com