Splash Screen Strategy
tg.lists at geistinteractive.com
Tue May 16 12:09:08 EDT 2006
I am using the "splash screen" Architecture for deploying an app. The
splash screen stack checks for updates and then launches the "Main"
stack. This part is all based on Chip's "altSplash" engine.
I want the "Main" stack to manage installing additional stacks and or
files. My current strategy is to load those additional stacks and
files into custom props in the Main stack. Then when a new version
of the main stack is downloaded it will spit out all of the stacks
and files that are loaded into it's custom functions into the
I thought that this would be easier then managing multiple downloads
from the internet for each additional stack and or file.
I am interested in hearing some opinions about this strategy. Does it
make sense to do it this way?
g e i s t i n t e r a c t i v e
More information about the Use-livecode