Self adjusting code?
bvlahos at mac.com
Tue May 4 22:41:10 CDT 2004
Welcome to this list and to Revolution.
What I think you are referring to is that Revolution "standalones"
cannot be modified. The is a restriction that the Mac OS does not have
but other OSs do so Revolution imposes this restriction on all
platforms. The standalones are the executables.
Fortunately, this is easily worked around. All you have to do is create
a standalone which opens your stack. The stack is completely modifiable
just like HyperCard and SuperCard by issuing save commands. This works
the same on all platforms and the stacks themselves are completely
portable across all platforms.
You can do what you suggest in your original email but it doesn't need
to be that complicated.
On May 4, 2004, at 8:24 PM, Randall Reetz wrote:
> My first post to this list...
> I am a SuperCard user (for 14 years). I am of course interested in
> Revolution's multi-platform output. However... in reading some of
> your tutorials, I came across a blurb outlining a restriction on
> making run-time changes to Revolution projects (stacks). I am
> interested in evolving code... projects that react to, optimize and
> adjust to their environment... who uses them and their intent, and
> available media, data and communications streams. How does one do
> this with Revolution? I can imagine a solution involving two
> concurrent projects... one running... the other treated as data
> file... adjusted by the first... then, periodically, the first
> duplicates the second (now there are three), launches the second which
> once launched, quits and deletes the first, then, gets down to the
> business of writing changes to it's inactive clone. Wow, that seems
> complex... but I can't quite imagine how else to do run-time
> self-adjusting code. How have you people solved this problem.
> Randall Reetz
> randall at thinkthink.com
> use-revolution mailing list
> use-revolution at lists.runrev.com
More information about the use-livecode