Specifications

CHAPTER 8

136

In some cases, options have multiple parent tags, as with the fonts options, such as compiler.fonts.managers

and

compiler.fonts.languages.language. Other options that require parent tags when added to a configu-

ration file include the

frames.frame option and the metadata options. The following sections describe methods

for determining the syntax.

Getting the configuration file tags

Use the help list option of the command-line compilers to get the configuration file syntax of the compiler

options; for example:

mxmlc -help list advanced

The following is the entry for the source-path option:

-compiler.source-path [path-element][...]

This indicates that in the configuration file, you can have one or more <path-element> child tags of the

<source-path> tag, and that <source-path> is a child of the <compiler> tag. The following example shows

how this should appear in the configuration file:

<source-path>

<path-element>.</path-element>

<path-element>c:/myclasses/</path-element>

</source-path>

</compiler>

Understanding leaf nodes

The help output uses dot-notation to separate child tags from parent tags, with the right-most entry being known

as the leaf node. For example,

-tag1.tag2 indicates that <tag2> should be a child tag of <tag1>.

Angle brackets (

< >) or square brackets ([ ]) that surround an option indicate that the option is a leaf node.

Square brackets indicate that there can be a list of one or more parameters for that option.

If the leaf node of a tag in the angle bracket is unique, you do not have to specify the parent tags in the configu-

ration file. For example, the help usage shows the following:

compiler.fonts.managers [manager-class][...]

You can specify the value of this option in the configuration file, as the following example shows:

<fonts>

<manager-class>flash.fonts.JREFontManager</manager-class>

</managers>

</fonts>