Specifications

321ADOBE FLEX 3
Building and Deploying Adobe Flex 3 Applications
• playerProductInstall.swf
• YourApp.swf
The AC_OETags.js file defines functions that the wrapper calls to embed the Flex application’s SWF file. It also
provides version checking methods. For more information about the AC_OETags.js file, see “Ab o u t t h e
AC_OETags.js file” on page 314.
In addition to using the AC_OETags.js file, you must also deploy the playerProductInstall.swf file in a location
that is accessible by the main application SWF file.
The files required by Express Install are located in the /templates/express-installation and /templates/express-
installation-with-history directories.
For more information about adding support for Express Install to your wrapper, see “Using Express Install” on
page 333.
Adding deep linking to your wrapper
Support for deep linking, also known as history management, is included by default in the wrappers generated by
Flex Builder. If you write your own wrapper, however, you must add it manually or use the HTML files in the
/templates directory as a base.
To add deep linking support, you reference the history.js file in a
<script> tag in your wrapper. The history.js file
records actions for deep linking. You must also deploy the following files with your wrapper:
• history.js
• historyFrame.html
• history.css
If you do not add deep linking support to your wrapper, you cannot use the BrowserManager in your Flex appli-
cation.
For more information about adding deep linking support to your wrapper, see “Deep Linking” on page 1065 in
the Adobe Flex 3 Developer Guide.
About the object and embed tags
The HTML templates included with Flex Builder and Flex SDK use the <object> and <embed> tags embed your
Flex application. In the case of Flex Builder, when you compile a project, Flex Builder sets the values for these tags
for you. For the SDK, you must manually edit the templates and set the values of these tags.