In article <2hhcc2$kmg at corax.udac.uu.se>, Gerard Kleijwegt <gerard at rigel.bmc.uu.se> writes:
> OOPS is NOT compatible with FRODO.
Ha! We have the *source code* for Frodo, so we can make
it compatible with *anything*! No such luck with O.
> Real men don't use FRODO, they write O macros.
What kind of "real men" we be talking about here, boy?
Some real people are end-users; others are programmers.
End-users don't *want* to waste their time writing macros.
They want a *program* that does what they want -- not a
As for programmers, we realise that macros can't do
everything. Try writing a *macro* that will prevent O from
sucking CPU cycles while doing nothing! (*Don't* tell me
to "just iconize the graphics window". Even if the user
pauses for *just a few seconds*, niceness demands that the
graphics program desist and give background jobs a crack at
In April of 1991 we tried out an early version of O for
the SGI. It didn't have side-by-side split stereo. (Yes,
I *know* this subsequently been added.) I sent Alwyn Jones
a message, saying that we were unlikely to use O until split
stereo was available. His e-mailed response was two words
long: "your loss". It's attitudes like that that make me
distrustful of monopolies, even by Alwyn.
> OOPS will look for bad or suspect disaster areas. It then
> generates a set of O macros which automatically take you
> from one disaster area to the next and tell you what's
> wrong/suspect about it, thereby reducing the time it takes
> you to rebuild your world by a factor of 2 to 10.
O.K., it's true we don't yet have Real Space Fit in
Frodo/TOM. We've got rotamers, an O-inspired DgLp, and mouse
controls, but I admit I envy you the Real Space Fit. Given
the will, we'll find a way.
misrael at csi.uottawa.ca Mark Israel