Re: [flexcoders] creationPolicy vs load/unload?

2005-03-21 Thread Joe Berkovitz
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 s

Re: [flexcoders] creationPolicy vs load/unload?

2005-03-21 Thread JesterXL
rankly, it feels good to use initialize everywhere, so I've never been comfortable using auto. I agree with Manish; create them dynamically. - Original Message - From: "Manish Jethani" <[EMAIL PROTECTED]> To: Sent: Monday, March 21, 2005 3:31 AM Subject: Re: [flexco

Re: [flexcoders] creationPolicy vs load/unload?

2005-03-21 Thread Manish Jethani
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 > applica

[flexcoders] creationPolicy vs load/unload?

2005-03-20 Thread Scott Barnes
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. I say this as if I have "Manager" application that loads sub-applica