🚀 go-pugleaf

In article <1992Jul20.021613.17250@CSUFresno.EDU> rhorowit@zimmer.CSUFresno.EDU (Rick Horowitz) writes:
>I have been wondering about this, too.  I heard that it was
>simply so Claris could make money by charging for a developers'
>kit, without needing to write another version of the program.
>Apparently, someone leaked the info (thank the gods).
>
>What I *can't* figure out is: if someone uncripples their 
>HC app, is there perhaps still a reason they would want to
>purchase the Developers' Kit?  What's in the Kit?
>
>Thanks for any replies. 
>
>||======================================================================||
>||  Rick Horowitz                  || If a tree falls across the road   ||
>||  CSUFresno, Philosophy          || and no one is there trying to     ||
>||  rick@csufres.csufresno.edu     || pass, does it block the road?     ||
>||  rhorowit@zimmer.csufresno.edu  ||          -Nick Serafimidis        ||
>||======================================================================||

First of all just enabling the scripting does not get you much unless you
have documentation to go with the functionality.  Claris offers two levels of
Hypercard.  Both come with the same basic software which includes  the all
important help stack as well as sample home stacks and other goodies.  The
first (cheaper) package from Claris includes some manuals, but they are
pretty terse and basically give you an overview of Hypercard and a manaul
that has the command syntax.  This is the package I have.  I have not seen
the more advanced developers kit, but it has additional manauls.

If you are not interested in the support stacks, I recommend you do the
"magic" trick and go out and buy Danny Goodmans HyperCard books for your
supporting documentation.  In fact even if you spring for the basic Hypercard
offering from Claris I recommend these books as a supplement.

Howard Kaplan
There are two packages that come from Claris.  Th