Datasheet

Luchner c01.tex V3 - 03/20/2008 2:29pm Page 4
Chapter 1: The Development Environment
In addition, if the amxmlc is set to debug mode when compiling the SWF file, you are given the opportu-
nity to debug your applications by running the ADL and Flash Debugger.
When you create an installer file for your AIR application you use the AIR Development Tool (ADT). AIR
installer files need to be code signed. It is recommended that you sign your AIR application by linking a
certificate from a certificate authority (such as VeriSign and Thawte), as it verifies that you (the publisher)
are the signer and that the application has not been maliciously altered — ensuring end users that they
are not installing a counterfeit version. You can create a self-signed certificate using the ADT tool as
well. Note that when using a self-signed certificate, your identity as the publisher cannot be verified
during installation. Moreover, if you later release an update to an existing application with a self-signed
certificate, then you need to use the original certificate when creating the installer file. The examples in
this book include the process of creating self-signed certificates.
In the next section you’ll jump right in and start building in order to see how the development environ-
ment you have set up by installing the SDK and setting System Paths to the command line tools will aid
your efforts to debug, deploy, and deliver your first AIR application — the familiar Hello World.
Building Your First Application
Now that you have the necessary files for deploying and packaging AIR applications, you should
carefully consider how you intend to develop your applications. Creating a directory in which you
will develop is just as important, as it is where you will spend most of your time in delivering a
product.
Although the examples in this book use the project directory structure outlined in the following sections,
it is not intended to replace any organization techniques you may already have. If the structure used here
does not agree with your workflow, you are encouraged to employ your approach and edit accordingly.
Some IDEs actually create a development directory within the
Documents directory on your machine —
User ➪ My Documents on Windows and User ➪ Documents on Mac. Though that is a viable solution
for your development environment, for the purposes of this book, create a folder called
Development
in the root drive on your machine — C:/ on Windows, the hard drive name on Mac. Within that folder
will reside a directory of the type of software you are using to develop your applications, including any
subdirectories of the projects therein.
On Windows:
1. Navigate to the root of the C:/ drive.
2. Create a folder titled Development .
3. Within that Development folder, create a folder titled AIR .
On Mac:
1. Navigate to the hard drive.
2. Create a folder titled Development .
3. Within that Development folder, create a folder titled AIR .
4