Re: Saving data in a stack ?STANDALONE
If you check the box in the Stacks section of Standalone settings that says Move substacks into individual stackfiles then you will be able to save all but the mainStack. One thing you might want to keep in mind if you are running multiple stacks off an anchor standalone file: Pay attention to the destroyStack and destroyWindow settings of the stacks. Besides the release of memory upon closing (if the above props are set to true), I've also found that: If more than one user is accessing the stacks (mulitple standalones running on a network, for example), one user's changes are not visible to another user (even if you explicitly do a save this stack on closing the individual stacks) unless the destroyStack and destroyWindow of the stacks are set to true. So the standalones, even if just a splash screen, seem to provide more than the engine itself KK ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Saving data in a stack STANDALONE
As a complete beginner with Revolution I¹ve found it very hard to get a grip on this. It¹s a big stumbling block for those used to Hypercard, where the IDE was taken for granted, and the concept of a standalone was unfamiliar. But the ability to deliver standalones cross-platform is a major attraction of Revolution so it¹s disappointing that such a key feature as how to save user changes to a stack is hard to grasp. I can understand that a standalone is an application, and as such shouldn¹t modify itself i.e. the user can¹t save any changes within the application. No problem write it out to a file, and read it back in on startup. But with structured data such as an Address Book you want to save the data as a stack that¹s the whole point! The answer given in the documentation is to set up a dummy stack as the mainstack, then do the work in a substack which is not itself compiled into a standalone, but left as a Revolution file (.rev). I simply couldn¹t get this to work, until I came across the answer in the lists.runrev archive go to the Standalone Settings item on the File menu - select the Stacks tab - click the box to Move substacks into individual stackfiles. This makes the substack persist as a .rev. The standalone knows where it is (automagically in the standalone's folder), and because it's a .rev it can be saved... Before finding this tip, I had been messing about for ages trying to get the standalone to pick up .rev files that were not part of its stack file. Ah well -- ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Saving data in a stack STANDALONE
As a complete beginner with Revolution I¹ve found it very hard to get a grip on this. It¹s a big stumbling block for those used to Hypercard, where the IDE was taken for granted, and the concept of a standalone was unfamiliar. But the ability to deliver standalones cross-platform is a major attraction of Revolution so it¹s disappointing that such a key feature as how to save user changes to a stack is hard to grasp. The difference is that you weren't making standalone applications in HC, unless you bought Heizer's Double-XX (as I did), in which case you were already living with this restriction. To make things more familiar for yourself, why not just distribute the Dreamcard player? That's what you did with HC. -- http://taoof4d.blogspot.com http://4dwishlist.blogspot.com On the first day, God created the heavens and the Earth On the second day, God created the oceans. On the third day, God put the animals on hold for a few hours, and did a little diving. And God said, This is good. ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Saving data in a stack STANDALONE
John Ridge wrote: As a complete beginner with Revolution I¹ve found it very hard to get a grip on this. It¹s a big stumbling block for those used to Hypercard, where the IDE was taken for granted, and the concept of a standalone was unfamiliar. But the ability to deliver standalones cross-platform is a major attraction of Revolution so it¹s disappointing that such a key feature as how to save user changes to a stack is hard to grasp. I can understand that a standalone is an application, and as such shouldn¹t modify itself i.e. the user can¹t save any changes within the application. No problem write it out to a file, and read it back in on startup. But with structured data such as an Address Book you want to save the data as a stack that¹s the whole point! The answer given in the documentation is to set up a dummy stack as the mainstack, then do the work in a substack which is not itself compiled into a standalone, but left as a Revolution file (.rev). I simply couldn¹t get this to work, until I came across the answer in the lists.runrev archive go to the Standalone Settings item on the File menu - select the Stacks tab - click the box to Move substacks into individual stackfiles. I can symphathize with the learning curve effort, but IMO the biggest conceptual hurdle isn't inherent in the process but rather introduced in the standalone builder which doesn't adequately label optional advanced features as such. All the engine requires to make a standalone is a stack and a little information about the resulting standalone (target file name, Windows info, Mac Finder info). Everything else is purely optional, and by not separating those from the essentials the standalone builder gives the impression that the task is more complex than it really is. Many people enjoy the Rev option of modifying the stack structure at build time (moving substacks in and out of separate stack files), but I'm a big fan of WYGIWYG: What you got is what you get. :) For myself I find that minimizing the differences between development and runtime helps minimize errors, nearly eliminating the range of possible issues that can arise from differences between the two environments. If you were to use this approach your development setup might look like this: |splash screen stack file| -- opens -- |Main UI stack file| By opens I simply mean that the splash screen stack opens the main UI stack in its openStack handler. When you build you get simply: --- | standalone executable | -- opens -- |Main UI stack file| --- No fuss, no muss, no relying on hidden processes altering your stack structure at build time, nothing more than the simplicity of working in and running the same setup. If using the advanced stack-morphing options has been confusing, you might consider this simpler WYGIWYG approach. -- Richard Gaskin Fourth World Media Corporation __ Rev tools and more: http://www.fourthworld.com/rev ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Saving data in a stack STANDALONE
As a complete beginner with Revolution Ive found it very hard to get a grip on this. Its a big stumbling block for those used to Hypercard, where the IDE was taken for granted, and the concept of a standalone was unfamiliar. But the ability to deliver standalones cross-platform is a major attraction of Revolution so its disappointing that such a key feature as how to save user changes to a stack is hard to grasp. I can understand that a standalone is an application, and as such shouldnt modify itself i.e. the user cant save any changes within the application If you check the box in the Stacks section of Standalone settings that says Move substacks into individual stackfiles then you will be able to save all but the mainStack. This is why people often make the mainStack a splash screen that does nothing except open one of the save-able sub stacks. HTH, Sarah ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
