Structuring an Application

[Sarah]

It depends whether you want to be able to save data to stacks or whether 
your app will save it's data elsewhere.

If you are saving stacks, you need to build the application with 
separate sub-stack files. In this case, the easiest way is probably to 
make the main stack your splash screen. It will contain the engine and 
the rest of the stacks will be writable and editable. There is an 
article about this on the Rev site in the Tip of the Week section.

If you don't need to make your stacks writable, then you can build the 
app as a single file. The main stack will be the first one opened but it 
can then open other stacks as required. Scripts in your main stack are 
available to the other stacks, but that works even if the main stack is 
no longer  an open window. Apart from this, there is nothing special 
about a main stack so it doesn't have to be always open or even the most 
used. It can be closed or left visible - you can control the substacks 
either way.

One further point - it is easy to move stacks around and designate the 
main stack at any stage so you can design your stacks as you go and then 
add a splash screen and make it the main when you are finished.

Cheers,
Sarah


On Tuesday, May 7, 2002, at 04:05  pm, Dave wrote:

> What's the best way to structure an Application in Rev?
>
> Should the main stack be the "about" window?  Since it's first to 
> display.
>
> Should the main stack be hidden so you can control the rest of your
> substacks as windows?
>
> Should the main stack be the most used window in the app?
>
> I'm not quite sure how to proceed.
>
> Many Thanks.
>
>
> -- Dave
> Retiarius Enterprises
>
>
>
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/use-revolution
>