Yep, browse the powerpoint (turn on the "notes" pages as well) and check
out the samples.
Collin, this is basically the purpose of the 2.0.1 Modules feature, so I
think its exactly what you want.
Shannon, the only way to not load classes that have already been loaded
is to omit them from linking. Check out the configuration options
"externs", "load-externs", and "external-library-path" for techniques
for excluding things from linking.
Note that if the definitions were previously loaded (either in the
current or a parent AppDom) it is harmless (just wasteful) to load them
again, as they will only get initialized once.
-rg
________________________________
From: flexcoders@yahoogroups.com
[mailto:[EMAIL PROTECTED] On Behalf Of Shannon
Sent: Sunday, December 10, 2006 4:46 PM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Re: Incremental loading or load-on-demand
And also how do we not load the classes (components, classes,
etc...)
that have already loaded?
There is some information on Flex 2.0.1 modules in Roger
Gonzalez's
MAX Presentation...
http://blogs.adobe.com/rgonzalez/
<http://blogs.adobe.com/rgonzalez/>
Be sure to check out the ppt.
--- In flexcoders@yahoogroups.com
<mailto:flexcoders%40yahoogroups.com> , "Collin Peters" <[EMAIL PROTECTED]>
wrote:
>
> Does anyone have some examples or links regarding
load-on-demand
> applications? By this I mean a Flex application that is made
up of
> many "sub applications" or modules that are loaded when
requested by
> the parent application. The modules are only loaded when they
are
> requested instead of being all loaded at application load
time.
>
> Is there any best practices defined for this?
>
> Regards,
> Collin Peters
>
