Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!necntc!ames!sdcsvax!ucbvax!ucdavis!caldwr!ack
From: ack@caldwr.caldwr.gov (David Ackerman)
Newsgroups: comp.sys.mac
Subject: Re: Hypercard
Message-ID: <109@caldwr.caldwr.gov>
Date: Thu, 15-Oct-87 03:42:14 EDT
Article-I.D.: caldwr.109
Posted: Thu Oct 15 03:42:14 1987
Date-Received: Sat, 17-Oct-87 05:32:22 EDT
References: <30594@sun.uucp> <253@nikhefk.UUCP> <255@nikhefk.UUCP>
Organization: California Department of Water Resources
Lines: 27


All this discussion about the difficulty of manipulating stacks while you
develop them got me to thinking: why not a "HyperWorkshop" or some such
application? The basic problem seems to be this: by trying to make your
stack as monkey-proof as possible, you end up getting in your own way. An
invisible button, restricting user access to most menu actions, intercepting
command-key events...all these will make your stack less vulnerable to
tampering, but will also get in the way as you are working on it. One
solution to this would be an enhanced version of Hypercard that would
*always* show buttons, fields, etc. One problem this might present is
if it could mess with stacks that were password protected. 

If the multi-access problems were solved, you could run "HyperWorkshop"
in one window to hack on a stack, while running Hypercard with that very
stack in another window to test it.

Hey Apple, how about putting the source for Hypercard on comp.sources.mac?
I'm sure someone could write such a beastie in a matter of months.
( very large :^) )


David Ackerman                            
California Department of Water Resources     ucdavis.edu!caldwr!ack  (Internet)
"It's the water, and a lot more..."       ...!ucbvax!ucdavis!caldwr!ack  (UUCP)

         The opinions expressed above are mine, not those of the State
         of California or the California Department of Water Resources.