In your question, "performance hit" could refer network performance
(i.e. latency to load the code/data for the views over the net) as well
as component initialization performance (latency to actually initialize
the components in the views).
So the answer probably depends on:
- the expected size of the SWFs that you would wind up loading/unloading.
- the degree to which you expect the user to actually instantiate all
the views at some point in their use of the application.
If the SWFs would be large relative to the size of some "shell
application", and the user would be unlikely to hit all the contained
views, then load/unload may be worth looking at.
Given what I've read about bugs in loadMovie'd Flex apps, though, it
might be a good idea to avoid this approach if you can.
. . . . ....j
Manish Jethani wrote:
> On Mon, 21 Mar 2005 16:48:51 +1000, Scott Barnes <[EMAIL PROTECTED]> wrote:
>
>
>>In terms of using typical default creationPolicy to load say screens
>>within a viewstack is it more of a performance hit to do it via this
>>way or would it be better suited to load/unload mxml swfs into your
>>application as needed.
>
>
> If the requirement is to load and unload views as and when they are
> needed, I would still go with createChild()/destroyChild() for the
> custom MXML/AS component (the view) instead of loading/unloading a
> SWF.
>
> Manish
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>
>
>
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/
