Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!umix!oxtrap!rich@oxtrap
From: rich@oxtrap (K. Richard Magill)
Newsgroups: comp.sys.mac.hypercard
Subject: Re: real object stuff in Hypercard
Message-ID: <4484@oxtrap.UUCP>
Date: 16 Sep 88 23:00:55 GMT
References: <68289@sun.uucp>
Sender: rich@oxtrap.UUCP
Reply-To: rich@oxtrap (K. Richard Magill)
Distribution: comp
Organization: Ocwen Trading - Ann Arbor
Lines: 14
In-reply-to: COMBS@SUMEX-AIM.Stanford.EDU (Dave Combs)

In article <68289@sun.uucp>, COMBS@SUMEX-AIM (Dave Combs) writes:
>One of the main problems I have in trying to use Hypercard for a relatively
>involved application is the lack of really useful variable storage.
>While Hypercard espouses the use of object-oriented programming techniques,
>and is built with a hierarchy from buttons and fields up through stacks,
>there is no real concept of "storage" except a) in fields, b) in variables
>which are local to a single message handler, or c) variables which are
>global to the entire system (or is it a single stack?).

I've been wondering why I can't let HC dispatch messages to an arbitrary object
with or without a screen representation.  Say, an external code resource?
Virtual cards?  (maybe a heap card with scratch fields that create
themselves...)
--