Q. data stacks and app design

Sarah sarahr at genesearch.com.au
Thu Oct 3 23:04:01 EDT 2002

It is a separate stack and can be hidden or visible. The main point is 
that it is not the mainStack of the file. When you build an 
application, you can either have it all in one file, or put the 
substacks in separate files. If the application is all in one file, it 
is read-only and no data can be saved as part of the application (you 
can always use external files to save). If you make an application with 
separate substacks, all but the main stack are writable and can store 
your data.


On Friday, October 4, 2002, at 01:22  pm, Alex Rice wrote:

> On Thursday, October 3, 2002, at 08:40  PM, Sarah wrote:
>> If you are going to be reading your saved data from another stack, 
>> the easiest thing is probably to save a copy of the data stack 
>> somewhere. Then your reader stack can just open the saved data stack 
>> at any stage. When you build your app, make sure it saves the 
>> substacks into separate files. This will allow your data stack to be 
>> saved (so long as it isn't the mainStack) either to it's default 
>> location or to your storage location.
> What is a data stack, just a hidden stack with a big Field in it?
> Alex Rice, Software Developer
> Architectural Research Consultants, Inc.
> alrice at swcp.com
> alex_rice at arc.to
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/use-revolution

More information about the use-livecode mailing list