You can develop AIR applications with the following Adobe
Flash Platform development tools.
For ActionScript 3.0 (Flash and Flex) developers:
For HTML and Ajax developers:
Installing the AIR SDKThe Adobe AIR SDK contains the following command-line tools
that you use to launch and package applications:
- AIR Debug Launcher (ADL)
- Allows you to run AIR applications without having to first
install them. See AIR Debug Launcher (ADL).
- AIR Development Tool (ADT)
- Packages AIR applications into distributable installation
packages. See AIR Developer Tool (ADT).
The AIR command-line tools require Java to be installed your
computer. You can use the Java virtual machine from either the JRE
or the JDK (version 1.5 or newer). The Java JRE and the Java JDK
are available at http://java.sun.com/.
At least 2GB of computer memory is required to run the ADT tool.
Note: Java is not required for end users to run AIR applications.
For a quick overview of building an AIR application with the
AIR SDK, see Creating your first HTML-based AIR application with the AIR SDK.
Download and install the AIR SDKYou can download and install the AIR SDK using the following
instructions:
Install the AIR SDK in WindowsDownload the AIR SDK installation file.
The AIR SDK is distributed as a standard file archive. To
install AIR, extract the contents of the SDK to a folder on your
computer (for example: C:\Program Files\Adobe\AIRSDK or C:\AIRSDK).
The ADL and ADT tools are contained in the bin folder in
the AIR SDK; add the path to this folder to your PATH environment
variable.
Install the AIR SDK in Mac OS XDownload the AIR SDK installation file.
The AIR SDK is distributed as a standard file archive. To
install AIR, extract the contents of the SDK to a folder on your
computer (for example: /Users/<userName>/Applications/AIRSDK).
The ADL and ADT tools are contained in the bin folder in
the AIR SDK; add the path to this folder to your PATH environment
variable.
Install the AIR SDK in LinuxThe
SDK is available in tbz2 format.
To install the SDK, create a folder in which you want to
unzip the SDK, then use the following command: tar -jxvf <path
to AIR-SDK.tbz2>
For information about getting
started using the AIR SDK tools, see Creating an AIR application
using the command-line tools.
What's included in the AIR SDKThe following table describes the purpose of the files
contained in the AIR SDK:
SDK folder
|
Files/tools description
|
bin
|
The AIR Debug Launcher (ADL) allows you
to run an AIR application without first packaging and installing
it. For information about using this tool, see AIR Debug Launcher (ADL).
The AIR Developer Tool (ADT)
packages your application as an AIR file for distribution. For information
about using this tool, see AIR Developer Tool (ADT).
|
frameworks
|
The libs directory contains code libraries
for use in AIR applications.
The projects directory contains
the code for the compiled SWF and SWC libraries.
|
include
|
The include directory contains the C-language
header file for writing native extensions.
|
install
|
The install directory contains the Windows
USB drivers for Android devices. (These are the drivers provided
by Google in the Android SDK.)
|
lib
|
Contains support code for the AIR SDK tools.
|
runtimes
|
The AIR runtimes for the desktop and for
mobile devices.
The desktop runtime is used by ADL to launch
your AIR applications before they have been packaged or installed.
The
AIR runtimes for Android (APK packages) can be installed on Android
devices or emulators for development and testing. Separate APK packages
are used for devices and emulators. (The public AIR runtime for
Android is available from the Android Market.)
|
samples
|
This folder contains a sample application
descriptor file, a sample of the seamless install feature (badge.swf),
and the default AIR application icons.
|
templates
|
descriptor-template.xml - A template of
the application descriptor file, which is required for each AIR
application. For a detailed description of the application descriptor
file, see AIR application descriptor files.
Schema files for the XML
structure of the application descriptor for each release version
of AIR are also found in this folder.
|
Setting up the Flex SDKInstall the Flex SDKBuilding AIR applications with the command-line tools requires
that Java is installed on your computer. You can use the Java virtual
machine from either the JRE or the JDK (version 1.5 or newer). The
Java JRE and JDK are available at http://java.sun.com/.
Note: Java is not required for end users to run AIR applications.
The Flex SDK provides you with the AIR API and command-line tools
that you use to package, compile, and debug your AIR applications.
If you haven't already done so, download the Flex SDK
at http://opensource.adobe.com/wiki/display/flexsdk/Downloads.
Place the contents of the SDK into a folder (for example,
Flex SDK).
Copy the contents of the AIR SDK over the files in the Flex
SDK.
Note: On Mac computers, make sure that you copy or replace
the individual files in the SDK folders — not entire directories.
By default, copying a directory on the Mac to a directory of the
same name removes the existing files in the target directory; it
does not merge the contents of the two directories. You can use
the ditto command in a terminal window to merge
the AIR SDK into the Flex SDK:ditto air_sdk_folder flex_sdk_folder
The command-line AIR utilities are located in the bin folder.
Setting up external SDKsDeveloping applications for Android and iOS requires that
you download provisioning files, SDKs or other development tools
from the platform makers.
For information about downloading and installing the Android
SDK, see Android Developers: Installing the SDK.
As of AIR 2.6, you are not required to download the Android SDK.
The AIR SDK now includes the basic components needed to install
and launch APK packages. Still, the Android SDK can be useful for
a variety of development tasks, including creating and running software
emulators and taking device screenshots.
An external SDK is not required for iOS development. However,
special certificates and provisioning profiles are needed. For more
information, see Obtaining developer files from Apple.
|
|
|