Specifications

CHAPTER 17
336
"bgcolor", "#869ca7",
"name", "MyFirstProject",
"allowScriptAccess","sameDomain",
"type", "application/x-shockwave-flash",
"pluginspage", "http://www.macromedia.com/go/getflashplayer"
);
}
In the second script block, change the src, id, and name parameters to match your SWF file’s name:
} else if (hasRequestedVersion) {
AC_FL_RunContent(
"src", "MyFirstProject",
"width", "100%",
"height", "100%",
"align", "middle",
"id", "MyFirstProject",
"quality", "high",
"bgcolor", "#869ca7",
"name", "MyFirstProject",
"allowScriptAccess","sameDomain",
"type", "application/x-shockwave-flash",
"pluginspage", "http://www.macromedia.com/go/getflashplayer"
);
}
When you edit these methods, you can also add flashVars variables, change the height and width of the SWF
file, and set other properties of the SWF file, if necessary. For more information about available properties, see
“About the object and embed tags” on page 321. For more information about adding deep linking support, see
“Deep Linking” on page 1065 in the Adobe Flex 3 Developer Guide.
6 Replace the value of the alternateContent variable with your own custom content. In this step and the next,
you can implement alternate methods of upgrading Flash Player for users who do not meet the requirements for
Express Install. For more information, see
“Alternatives to Express Install” on page 338.
7 Replace the HTML code found within the <noscript> tag with your own custom content. For more infor-
mation, see “Alternatives to Express Install” on page 338.
8 Deploy the playerProductInstall.swf file included in the /templates/express-installation directory to your web
server.
By default, you should deploy this file to the same directory as your Flex application. If you deploy it to another
location, you must update the wrapper to point to this new location. This file is also included in your Flex
application’s bin directory in Flex Builder.