Splash Screen Strategy

[Todd Geist]

Hello,

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  
appropriate places.

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?

TIA

Todd
-- 

Todd Geist
______________________________________
g e i s t   i n t e r a c t i v e