Packaging Your AIR Application
When you're ready to package your application, choose the AIR Application & Package Settings command, which will open the dialog shown in Figure 2
. For simple testing, you can usually accept all the default values in this dialog, but you must be sure to test your movie after any changes, before compiling. The Test Movie command generates a current SWF that will be used to create the AIR application.
Figure 2. Putting the Baby to Bed: Usually you can accept all the default values in the AIR Application & Package Settings dialog, but be sure to test your movie after any changes and before compiling.
In this case, you'll want to make sure one additional change is made, which is switching the Window Style menu to Custom Chrome (transparent). This change will cause the Flash stage to disappear, and only nontransparent pixels will show in the application. Optionally, you can also choose which icons are used for your application by choosing pre-created PNGs in 16-, 32-, 48-, and 128-pixel square sizes.
You may notice in Figure 2 that these options appear disabled, and the "Use custom application descriptor file" checkbox is checked. If desired, you can configure the autogenerated XML document yourself. You may find this approach easier to repurpose from project to project, for example. (An example is included here.) If so, check the aforementioned checkbox, and browse for this file:
<?xml version ="1.0" encoding="utf-8" ?>
<application appId="com.air.flash.HelloWorld-AS" version="0.1"
A simple Hello World application with the following features:
draggable, minimizeable, closeable, shows/hides assets,
writes text file to desktop.
<copyright>Creative Commons Attribution-ShareAlike 3.0</copyright>
<rootContent systemChrome="none" transparent="true" visible="true">
<!-- <handleUpdates/> -->
<!-- <fileTypes> <fileType> <name>adobe.FlashFile<name>
<extension>swf Adobe Flash File</description>
|Author's Note: In this described Flash CS3 workflow, you may want to put your custom XML file in a separate directory. Every time the movie was tested a new copy of the XML file was generated, overwriting the custom file without as much as a fare-thee-well.|
Also, once you've set up the dialog or XML file the first time, you can then skip immediately to the AIRPackage AIR File command.
Again, this entry level "first AIR application" tutorial was pushed a bit to demonstrate the AIR-specific commands. If you are just interested in creating a custom shaped window for your linear Flash animation, you can do that without any extra work at all. If this tutorial seemed like a breeze, dig in deeper. There are several impressive sample applications in the related resources list.