You can link the Flex framework as a runtime shared library (RSL). This creates a framework_xxx.swf and .swz file that contain the entire flex framework instead of including the components you use in your application. You application becomes smaller but the framework is pretty big. The advantage is flash players cache the framework so once someone loads that version of the framework, they never need it again.
In Flex Builder you change the framework linkage to RSL in the "Flex Builder Path" | "Library Path" properties of the project. http://www.onflex.org/ted/2008/01/flex-3-framework-caching.php http://labs.adobe.com/wiki/index.php/Flex_3:Feature_Introductions:Flex_3_RSLs#How_to_use_the_Flex_Framework_as_an_RSL On Thu, May 15, 2008 at 1:18 PM, <[EMAIL PROTECTED]> wrote: > I'm building simple apps in Flex as I'm quite comfortable with the > development environment compared with Flash. I've noticed that the simplest > possible application – just an > <mx:Application><mx:Canvas></mx:Canvas></mx:Application> - weighs in around > 148KB when exported as a release build. > > What, if any, strategies are available for optimizing the size of SWFs > produced by Flex? > > Best regards, > > Roger >
