Notes on creating your first Adobe Air application
Posted on: March 5, 2008
The base documentation from Adobe is pretty good, but there are a couple of gotcha’s which aren’t immediately clear.
- You need to copy AIRAliases.js from
<air install dir>/frameworks
into your application directory (the same place you’ve placed you xml config file and sample html file.)
If you try to test the sample application without doing this, you’ll get an error. - My Windows setup is weird about PATH variables for some reason. If you get the standard ‘adl is not recognized as an internal command’ error, you can simply add the path to the adl executable into your command line query like so:
<air install dir>/bin/adl.exe HelloWorld-app.xml
- By default, when an application is packaged, the ADT process attempts to contact a time server to generate a timestamp. If you use a proxy server to connect to the internet, you’ll get a ‘connection refused’ error.
You can get around this by adding ‘-tsa none‘ before the file component of the command like so:adt -package -storetype pkcs12 -keystore sampleCert.pfx -tsa none HelloWorld.air
HelloWorld-app.xml HelloWorld.html AIRAliases.js
5 Responses to "Notes on creating your first Adobe Air application"
June 6, 2008 at 12:39 pm
Hi Damon,
AIR is getting a lot of adoption, so I imagine the developer tools (and process) will get much better over time.
April 20, 2010 at 6:24 pm
Hi All,
This is very helpful. I just want to ask, for example, i have many files to compile, should i type all of the filename in the command line? Is there any other way to make it add at one time?
Thank you.
April 21, 2010 at 8:56 am
Hi JR,
I’m not 100% sure on this one, but you could try adding the directory names where the files reside and see if it auto-adds them in during the compile process.
I doubt Adobe expects people to name every file to compile, but then again I could be wrong.
Paul
Hi Paul,
I have a question regarding window. can we make many child window for air? What i’m trying to do is that i have a parent window with many modules in it… then if i click one module, it will create new root window and if i close it then open again, it will now create two instance of that window… how can i manipulate many windows and let the child access variables or functions from the parent window?
Thank you.
paul bennett 
June 6, 2008 at 10:03 am
Yo Paul, Thank you for your posting… It was very helpful… I guess I’m alittle put complicated this is to create an exe …Adobe Air is pretty cool, Adobe needs to streamline the whole process alittle. still way to hard to do something that should be a click of a button. i feel like I’m using Visual Studio 2003 all over again… files and folders everywhere that I’m some how held responsible for making, even though I didn’t put them there… All this to make an executable… heres an idea Adobe…. make a (Compile App button) whoa…