Hey i think i came across something very useful. first i have to say if your 
app is big, split it up into modules. and also use rsl. now i came across this 
in the flex help. have not tried it yet but it looks like it might help brind 
down the size of the modules. here it is

Reducing module size 
Module size varies based on the components and classes that are used in the 
module. By default, a module includes all framework code that its components 
depend on, which can cause modules to be large by linking classes that overlap 
with the application's classes.

To reduce the size of the modules, you can optimize the module by instructing 
it to externalize classes that are included by the application. This includes 
custom classes and framework classes. The result is that the module includes 
only the classes it requires, while the framework code and other dependencies 
are included in the application.

To externalize framework classes with the command-line compiler, you generate a 
linker report from the application that loads the modules. You then use this 
report as input to the module's load-externs compiler option. The compiler 
externalizes all classes from the module for which the application contains 
definitions. This process is also necessary if your modules are in a separate 
project from your main application in Flex Builder.

Create and use a linker report with the command-line compiler

Generate the linker report and compile the application:mxmlc 
-link-report=report.xml MyApplication.mxml

The default output location of the linker report is the same directory as the 
compiler. In this case, it would be in the bin directory.

Compile the module and pass the linker report to the load-externs option:mxmlc 
-load-externs=report.xml MyModule.mxml


Reply via email to