Specifications

137ADOBE FLEX 3
Building and Deploying Adobe Flex 3 Applications
</compiler>
However, the <manager-class> leaf node is unique, so you can set the value without specifying the <fonts> and
<managers> parent tags, as the following example shows:
<compiler>
<manager-class>flash.fonts.JREFontManager</manager-class>
</compiler>
If the help output shows multiple options listed in angle brackets, you set the values of these options at the same
level inside the configuration file and do not make them child tags of each other. For example, the usage for
default-size (
default-size <width> <height>) indicates that the default size of the application is set in a
configuration file, as the following example shows:
<default-size>
<height>height_value</height>
<width>width_value</width>
</default-size>
Using tokens
You can pass custom token values to the compiler using the following syntax:
+token_name=value
In the configuration file, you reference that value using the following syntax:
${token_name}
You can use the @Context token in your configuration files to represent the context root of the application. You
can also use the
${flexlib} token to represent the frameworks directory. This is useful if you set up your own
configuration and are not using the default
library-path settings.
The default value of the
${flexlib} token is application_home\frameworks.
Appending values
In a configuration file, you can specify the append attribute of any tag that takes a list of arguments. Set this
attribute to
true to indicate that the values should be appended to the option rather than replace it. The default
value is
false.
Setting the
append attribute to true lets you compound the values of options with multiple configuration files.
The following example appends two entries to the
library-path option:
<library-path append="true">
<path-element>/mylibs</path-element>
<path-element>/myotherlibs</path-element>
</library-path>