🚀 go-pugleaf

In article <1992Oct27.162538.10288@next.cambridge.ma.us>  
simsong@next.cambridge.ma.us (Simson L. Garfinkel) writes:
|> Its just that simple.  WordPerfect did it wrong.  Co-eXist did it wrong.   
|> Executor did it wrong, but then they fixed it (an easy fix). SBook 2.0 did  
it  
|> wrong, but SBook 2.05 does it right.
Let me get this straight, you _wrote_ SBook. You reviewed the ADB keyboard
in the winter 92 NeXTWorld. So when did you first notice that SBook was
feeding from the forbidden fruit?

But in any case, thanks for the update on SBook. You'll be happy to know
it's on my list of packages to look at buying. Now I know to hold out for a
demo of 2.05. What's the policy on fixing copies that are already in the
field ie if someone is using SBook and they get ADB and SBook stops working?
Is there a number they should call? How much will it cost? Can they get it via
FTP or NeXTMail? And if I buy a copy of SBook from NeXTConnection tonight
will it be 2.05?

And a note to other developers. If Simson can _almost_ admit he fed at the
forbidden keycodes then you too can find salvation by coming forward and
confessing your "sin". If you won't do it for yourselves, then please consider
doing it for your users. And I again put forth my offer that any non-ADB
equipped brother seeking to see if his program is a sinner may contact me via
e-mail for details on "Brother Scotty's ADB Equipped Temple of Salvation."
And remember brothers, non-ADB compliance doesn't just happen to "Emulators",
it can happen to straight NeXTSTEP applications as well. Many thanks to
Brother Simson for this valuable object lession.

Scotty