If you are concerned about SWF size and the total amount of bytes downloaded, be sure to use the framework RSLs. They are increasingly likely to be cached and save you significant download costs. After that, use modules to load classes not needed at startup “later” and “on-demand”.
If you are concerned about runtime-memory usage, once a class is instantiated once, if the instance is garbage collected, the next instance you create won’t take up more memory. But the first time you use a class to make an instance or refer to statics, it will initialize the class and take up a chunk of memory, but not until first accessed. There are hundreds of classes in most Flex swfs so 3 additional popups classes won’t be noticed. On 2/24/10 9:35 PM, "ZIONIST" <stinas...@yahoo.com> wrote: Hi guys, in my research on how to reduce the size of a flex application swf, i was led to believe that classes are one of the factors that contribute to the size of any flex swf and in order to reduce the size, one has to make sure he only calls the classes that are needed. but again i noticed that certain classes are used more than once in an app, take for example, popup class, i my have about three titlewindow custom components that i use for popup and on each i call the popup class. is there a way to call all classes used only once in the main app file and use them throughout the all application like the way we use css and if so will that help bring down the size of the complete application? -- Alex Harui Flex SDK Team Adobe System, Inc. http://blogs.adobe.com/aharui
