--- Phil Davis [EMAIL PROTECTED] wrote:
One common way to handle this is to organize
your app like this:
- the main app consists of the engine your
splash screen stack only.
This keeps the executable small so it opens
quickly when the user starts
the app.
- the splash screen stack
A very simple example would be where you have your mainstack (called
splashStack) as a splash screen, and your actual logic in a
substack (called logicStack).
In the script of stack splashStack
on startUp
show me
open stack logicStack
end startUp
in the script of stack logicStack
on
Mark Smith wrote:
A very simple example would be where you have your mainstack (called
splashStack) as a splash screen, and your actual logic in a
substack (called logicStack).
In the script of stack splashStack
on startUp
show me
open stack logicStack
end startUp
in the script of
On May 2, 2006, at 7:54 PM, Richard Gaskin wrote:
Mark Smith wrote:
A very simple example would be where you have your mainstack
(called splashStack) as a splash screen, and your actual logic
in a substack (called logicStack).
In the script of stack splashStack
on startUp
show me
Hi Eric,
Here's a quick example you can play with and modify as you like. It
isn't meant to be the be-all-end-all, it just illustrates the one app
structure idea I was promoting.
http://pdslabs.net/stacks/sampleApp.zip
Just unzip, double-click 'appSplash.rev' and away you go.
Phil
