DunbarX wrote:
So the standalone maker creates a new kind of stackfile, the standalone, which contains the various stacks that were attached. I get it now. I hope I remember it.
This is one of those areas where it's much like HyperCard: the runtime engine gets bound to the stack file to make the standalone.
The big difference is that HC only ran on Classic, where the runtime engine code was stored in the resource fork and the OS had no restriction on that code modifying the data fork.
On OS X, Windows, and Unix/Linux, an executable file cannot modify itself, so Rev standalones can't save changes to their own file.
But as Jacque noted, you can set up the Standalone Settings to break out substacks into separate stackfiles at build time, so you can keep everything in one file while you're working and still have them as modifiable "satellite" stacks at runtime.
Personally, I like to minimize the differences between development and runtime when I'm working to avoid any unexpected gotchas in deployment, where diagnosing things is much harder of course because there's no IDE.
So I tend to break out any separate stackfiles up front rather than leaving it to the Standalone Builder; it means I need to be more conscientious when saving, but also means my dev setup more closely matches my runtime, so hopefully if there are any issues in finding files I'll know it in the environment where I can debug it conveniently.
-- Richard Gaskin Fourth World Rev training and consulting: http://www.fourthworld.com Webzine for Rev developers: http://www.revjournal.com revJournal blog: http://revjournal.com/blog.irv _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
