Aloha, to all:
Thanks to all for testing our small Metacard Site/stacks. We am getting a
lot of super suggestions for strategy. . .
Several have suggested creating a standalone of the #1 "portal stack" that
is used to download the larger cirriculum stack and this way avoid having
users download first the engine and then the stack itself. Since our
intention is not to deliver a trial developer version then there is no
reason to separate the engine, so goes the logic, i.e. we create a kind of
unique, dedicated plug-in or http client.
Question: When you build a standalone, are ALL of Metacard's code resources
loaded, or only the code required to run the scripts for that particular
stack. (which is how Supercard SA's work as far as I can remember.)
The issue will be: if you later download a stack whose syntax requires code
resources that are not in the initial standalone, and you haven't delivered
the full engine at any point in the users history then your latest "more
advanced" stack will break. We are making a lot of assumptions here. Scott,
bottom line?
Thanks
Hinduism Today
Sivakatirswami
Editor's Assistant/Production Manager
www.HinduismToday.com
[EMAIL PROTECTED]
Archives: http://www.mail-archive.com/metacard%40lists.best.com/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.
