Re: {Disarmed} Re: {Disarmed} [flexcoders] Flex SWF running slow

2007-05-11 Thread Jurgen Beck
Frame rate is still very much part of Flex, which by default uses 24 
frames per second. You can change that during compile time.


Here is a good write-up on frame rates: 
http://ajax.sys-con.com/read/303778.htm


Question: Are the 300 plus UI elements the checkboxes, labels, etc.that 
you have in the application?


They seem to be showing up almost right away, at least for the first 
tab. If you are writing your application code logically you can employ a 
lazy loading scheme whereby data is not loaded (including data binding) 
until it is really needed. Again, I haven't looked at your code, so I'm 
not sure how much data you are pulling in.


One thing you could do is temporarily comment out any code that actually 
loads data and then see how your application behaves. If this eliminates 
the delay, you can start enabling the data loading mechanism one by one 
to see where the delay is introduced.


Jurgen

alex steel wrote:


thank for looking

It happens to me without any interaction
I know for service browser and everything is ok,
I still think it have problem with adding 300 ui elements

with my flash experience I would break it in smaller chunks, for
example 40 frames per second, break it in 8 per frame, it would slide
through it

how can I do such a thing in Flex ?

if that isn't problem I would still have good ad to my Flex experience
and future issues

I didn't looked about how Flex execute larger chunks of code
does it try to do it in one frame, or it's truly frame=free ?

 


RE: {Disarmed} Re: {Disarmed} [flexcoders] Flex SWF running slow

2007-05-11 Thread Tracy Spratt
Have you set creationPolicy=all anywhere?

Tracy

 



From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Jurgen Beck
Sent: Friday, May 11, 2007 5:18 PM
To: flexcoders@yahoogroups.com
Subject: Re: {Disarmed} Re: {Disarmed} [flexcoders] Flex SWF running
slow

 

Frame rate is still very much part of Flex, which by default uses 24
frames per second. You can change that during compile time.

Here is a good write-up on frame rates:
http://ajax.sys-con.com/read/303778.htm
http://ajax.sys-con.com/read/303778.htm 

Question: Are the 300 plus UI elements the checkboxes, labels, etc.that
you have in the application?

They seem to be showing up almost right away, at least for the first
tab. If you are writing your application code logically you can employ a
lazy loading scheme whereby data is not loaded (including data binding)
until it is really needed. Again, I haven't looked at your code, so I'm
not sure how much data you are pulling in. 

One thing you could do is temporarily comment out any code that actually
loads data and then see how your application behaves. If this eliminates
the delay, you can start enabling the data loading mechanism one by one
to see where the delay is introduced.

Jurgen

alex steel wrote: 

thank for looking

It happens to me without any interaction
I know for service browser and everything is ok, 
I still think it have problem with adding 300 ui elements

with my flash experience I would break it in smaller chunks, for
example 40 frames per second, break it in 8 per frame, it would
slide
through it

how can I do such a thing in Flex ?

if that isn't problem I would still have good ad to my Flex
experience
and future issues

I didn't looked about how Flex execute larger chunks of code
does it try to do it in one frame, or it's truly frame=free ?