Specifications

293ADOBE FLEX 3
Building and Deploying Adobe Flex 3 Applications
The configuration file syntax is also different between SDK 2.0.1 and SDK 3. If you use a customized flex-
config.xml file, you must ensure that you match its syntax to the syntax of the SDK that you compile with. If you
change SDKs, you might need to change the configuration file.
The following table lists the differences between the configuration files:
Signed framework Runtime
Shared Libraries (RSLs)
Applications are not compatible with signed
framework RSLs.
Applications are compatible with signed framework
RSLs.
Icons for disabled components When the
disabledIcon property is set to
null, the icon is invisible when the component is
disabled.
The icon for a disabled component does not disap-
pear when the disabledIcon property is set to
null. To mimic the Flex 2.0.1 behavior, you can create
a style that specifies
null for the classes in the appro-
priate icon properties. For example:
RadioButton {
icon:ClassReference(null);
disabledIcon:ClassReference(null);
selectedDisabledIcon:
ClassReference(null);
}
You can set remaining icon properties, such as
downIcon and overIcon, to the appropriate skin
class; for example, mx.skins.halo.RadioButton.
SDK 2.0.1 SDK 3
<flash-type>
true
</flash-type>
<advanced-anti-aliasing>
true
</advanced-anti-aliasing>
<!-- <locale>en_US</locale> --> <locale>
<locale-element>en_US</locale-element>
</locale>
<!--
<source-path>
<path-element>locale/{locale}</path-element>
<path-element>string</path-element>
</source-path>
-->
<!--
<source-path>
<path-element>string</path-element>
</source-path>
-->
<external-library-path>
<path-element>
libs/playerglobal.swc
</path-element>
</external-library-path>
<external-library-path>
<path-element>
libs/player
</path-element>
</external-library-path>
Difference Behavior in SDK 2.0.1 Behavior in SDK 3