If it were me, I would create an application stub with no display
objects and a module loader to load in different modules as required.
On application complete event, load in the initial module. Then, if the
user wants to continue, load in the main module. If you break up your
application into different categories/area/whatever the you can use a
module for each of the different categories/area/whatever.
If you need to pass data between the different modules, create an
interface that they all implement.
In my application, I have 26 modules and counting. In the main stub file
I have a custom component that implements an app control bar and a VBox
to load my modules in to...
<mx:VBox width="100%" height="100%" paddingTop="0" paddingBottom="0"
paddingLeft="0" paddingRight="0">
<mx:ModuleLoader id="currentModule" ready="onModuleReady(event)"
width="100%" height="100%"/>
</mx:VBox>
So, depending on events I receive from various modules, I change the url
property of the module loader to load in a new module. When the new
module becomes ready, I inject the data that I have into it using an
interface that all modules implement.
Best Regards
Steve
--- In [email protected], dorkie dork from dorktown
<dorkiedorkfromdorkt...@...> wrote:
>
> In my intial application swf I've kept it small to load quickly. If
> the user decides to use the application I want to load that into the
> initial app swf. How do I do this? Should I create a new instance of
> system manager and set it to load the new swf (not sure how)? Should I
> use a loader to load the main application? Will that keep the initial
> swf in memory thus using up that memory?
>
> JP
>
