On 6/8/05, Shlomi Cohen <[EMAIL PROTECTED]> wrote:
> I know that Flex Explorer sample implemented something similar with the
> mx:Loader tag. where every application is loaded by the URL sent to the
> loader object.
> the only design fault i can see here is that every module have to be in its
> own mx:Application tag otherwise the loader can't load it.
>
> is there a better way ? what is the best practice here ?
The advantage of splitting them into separate applications is that
instead of having one large SWF file, you have several small ones.
What are the disadvantages?
You can use createChild() and destroyChildAt() to create and destroy
children on the right panel. Look for these APIs in the Flex API
docs. They belong to the View class.
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/flexcoders/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
