Animator: XML Motion →← Apollo = AIR

A Breath of Flash AIR

Apollo has officially been renamed AIR. Now you want to know how to use Flash CS3 to begin developing AIR applications. After downloading the SDK you will notice it does not contain a global.swc file as the previous version did. Reading the docs would make you think you can only use an HTML editor or Flex 3 to develop for AIR currently. Fear not fellow Flashers help is on the way.

Basically you will need to download the Flex 3 beta and install it. After installing Flex 3 beta follow these steps:

  1. Find the airglobal.swc in the following directory Adobe Flex Builder 3/sdks/moxie/frameworks/libs/air/
  2. Copy airglobal.swc to Adobe Flash CS3/Configuration/ActionScript 3.0/Classes/
  3. Rename playerglobal.swc in that directory to something else (ie. oldplayerglobal.swc)
  4. Rename airglobal.swc to playerglobal.swc



Start Flash CS3 and you can begin publishing AIR based swf files as before. Remember you will need to execute your applications via the command-line currently. You got moxie now kid ;-)

June 11th, 2007  by Stephen  /  5 Comments

Comments on “A Breath of Flash AIR”

  1. Note that when testing in the IDE the program will still be running in the Flash Player, not AIR. So while you won’t get compiler errors, you will get runtime.

    To test in AIR, you’ll need to use Adobe’s ADL and ADT command line utilities. flash.system.Capabilities.playerType == “Desktop” will be exceptionally useful in discerning whether or not you can run an AIR-specific method.

    Jamie on June 11th, 2007 at 9:31 pm
  2. Thank you thank you! This is exactly what I was looking for!

    chuck on June 12th, 2007 at 9:07 am
  3. Thanks?

    Kevin Sweeney on June 14th, 2007 at 12:16 am
  4. […] As mentioned on Big SpaceShip Labs this is a runtime errors not compile time errors, and since they are so low level you can’t try/catch them. Error boxes is the last thing your viewers want to see as the first thing they hit you app! import flash.filesystem.*; import flash.system.Capabilities; import com.troyworks.io.*; […]

    TroyWorks » Blog Archive » One swf to rule them all: Coding a single swf for both web and AIR runtimes. on September 21st, 2007 at 4:11 pm
  5. […] As mentioned on Big SpaceShip Labs this is a runtime errors not compile time errors, and since they are so low level you can’t try/catch them. Error boxes is the last thing your viewers want to see as the first thing they hit you app! […]

    TroyWorks » Blog Archive » One swf to rule them all: Coding a single swf for both web and AIR runtimes. on December 10th, 2007 at 7:57 pm