I would hope the difference between Group and SkinnableContainer isn't
making a difference in your app. The main Application is already a
SkinnableContainer so you already have the code loaded and ready to go.
You could just warp your stuff with NavigatorContent tags
So, you are saying that if one component is loaded into memory the others won't allocate more memory (for the inherited code). Is it? Then, your answer makes sense. Since the application is also a SkinnableContainer.
For example, a container with two buttons the first will allocate 12k in memory to allocate all code. The second will allocate only 1k beacuse the greater part was allocated by the first?
This is useless. Because I want to use a Group to optimize the code. Wrapping my stuff I'll have more code.
Instead of wrapping, I could just use the NavigatorContent.
Thanks for your answer.
1 person found this helpful
Lol, okay, how many minutes have you been using Flex ? If you were serious about optimizing code, due to memory constraints, you wouldn't even be arguing about mxml , group vs skinnablecontainer. You would avoid the overhead provided by mxml components and instead write your components in AS3. However, I don't think you are doing that. I would take Alex's advice, and use a skinnable container, if you are on a platform where 12 k is going to make that much of a difference, you probably shouldn't be using Flex.
Protip: Get some experience with the framework and its various workflows. Then , after profiling your app, you can begin to optimize. But starting to optimize a container because you read it on some blog is the wrong way to proceed.
Ok. You are right.
I've been using Flex4 for a few time. So, I was thinking the perfomance between them are much different. My precipitation...
P.S: 12k was just an arbitrary value to exemplify.