Thanks, Alex. Unfortunately that is the main problem as I let users add graphics on the fly to create their artwork. And graphics are small swf animations, really simple ones. How is adding swf's different in this regard than adding jpegs, gifs or png's on the fly? Also is there a limit set? Because after adding lots of them, some of them just start to disappear and all I do is stack them with addChild(). Can we expect same performance issues when adding lots of visual objects such as buttons, canvases, etc...? If I add 100 simple swfs and 100 button controls, will it behave the same?
On Sun, Jun 22, 2008 at 3:37 AM, Alex Harui <[EMAIL PROTECTED]> wrote: > There are no workarounds. Good design for Flash minimizes use of > resources. The profiler can help you tune things, but if you use lots of > SWFs you're going to pay a price. However, that may not be your main > problem, and the profiler can help you determine that. > > > ------------------------------ > > *From:* [email protected] [mailto:[EMAIL PROTECTED] *On > Behalf Of *Alen Balja > *Sent:* Saturday, June 21, 2008 3:57 AM > *To:* [email protected] > *Subject:* Re: [flexcoders] Flex Efficiency > > > > Alex, do you have any more info on the subject, especially what are the > workarounds? I too am using lots of really tiny and simple external swf > animations and performance is really really bad. If I remember correctly > it's much worse than Flash Player 7. > > > > The profiler will help you find inefficiencies in your app. > > > > Loading lots of SWFs is, of course, going to eat resources. > > > > > > >
