In terms of passing the config data through to modules we create an interface for each module that is used by the shell to pass data via public methods to the loaded module on the ready event.
--- In flexcoders@yahoogroups.com, "Alex Harui" <[EMAIL PROTECTED]> wrote: > > Flashvars should be ready right away, long before creationComplete. How > are you accessing them? > > > > ________________________________ > > From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On > Behalf Of Richard Rodseth > Sent: Tuesday, April 29, 2008 2:30 PM > To: flexcoders@yahoogroups.com > Subject: [flexcoders] Application initialization and runtime config > > > > The application I'm working on has a dependency on runtime > configuration (flashVars) that needs to be met before any service > calls are made. > > I have an MVCS architecture, quite modular, though not yet using > mx:Module. > > I was unable to fetch the data for each module using creationCompete() > because the flashVars were not yet available, so for now the top level > creationComplete() just retrieves the config, then calls a controller > method to initialize the application. I could extend that to call an > interface implemented by each "module". > > Or, I suppose I could use view states bound to a flag, and place the > application shell in a "configuring" state, then in a "configured" > state. > > Any other approaches people have found to work well? Thanks. >
