Use of a profiler will help you identify the fat. If a component is not visible, it shout not be instantiated. Use deferred instantiation, states, or some other technique to only instantiate what you need.
HTH, -Alex On 11/19/16, 2:13 PM, "bilbosax" <[email protected]> wrote: >So I tried changing to mx:Label first and did not see any relative >improvements in speed from spark. I like the way spark looks better, so I >decided to stick with it, especially because I do not know if more mx >components will be slowly taken away from mobile over time. Next, I >reduced >the number of groups down to none in the itemrenderer, and reduced the >number of labels from 30 down to 9. This did improve performance from >5000ms down to around 2500-3000ms, so it is a definite improvement but not >nearly enough. I am going to try and cut some additional fat out of my >app, >especially the other components involved in the transition to see if I can >improve performance. The main page of the app has 13 groups and a border >container all laid out in percentages, 3 mobilegrids(only 1 visible at a >time), 4 buttons, 3 texinputs, 12 dropdownlists, 16 labels, and 4 fxg >graphics. All of these things I assume have to be sized and drawn as the >transitions take place. I am not positive of this, it is possible that my >list just slides over the top of all of these items but they all remain in >place. I wish I knew if they were actually removed from the display >list. >But I figure it can't hurt to try a custom layout instead of percentage >based groups to speed up transitions. In the end, I will not be happy >unless I can get these transitions to happen in under 1000ms. I will keep >updating this thread, but I am slow at this type of programming so please >bear with me. > > > >-- >View this message in context: >http://apache-flex-users.2333346.n4.nabble.com/Scout-What-does-this-mean-t >p14126p14168.html >Sent from the Apache Flex Users mailing list archive at Nabble.com.
