I keep advocating single-click builds and it's time to put my money where my mouth is. This article will show you how to set up Flash Builder to rebuild and package an AIR Native Extension with one click. Read More
Let me ask you a question. Let's say you've written the code for your AIR Native Extension, native library, AIR library and all that. How many steps does it take to build and package this in an .ANE file? Let's count: 1... Read More
This post will show you how to package an ANE - AIR Native Extension - on the command line.
The bad news first: it's a nuisance - a lot of file copying, renaming and deleting before you even get to run any command-line tools. Now the good news: all of this can be automated with a script - see the note at the end of this article. Read More
So you have started writing an AIR Native Extension (ANE). You've got a pretty good idea of how AIR loads and unloads it from memory and know that you need an Extension Context to tell AIR about what functionality your native code exposes. The infographic in this article will show you the mechanism of making native function calls from ActionScript. Read More
Yesterday we saw how a Native Extension is loaded in memory: what calls are made and in what order. Unloading the extension follows a similar scenario, except:
A native extension that you app uses only gets loaded in memory if the app makes a call into it. We have so far covered a couple of steps that happen at that point: extension initialization and extension context initialization. Let us now look at the process of loading the ANE in terms of what order these calls are made in and which parts of the system make them. Below is a diagram that illustrates what happens when an iOS ANE is loaded in memory: Read More
A lot of you have already downloaded our Camera Native Extension for iOS and will be thrilled to hear about the latest updates to it: Read More
In Java FREContext is a class that you extend, which serves as a middleman between ActionScript and your native Java code.
You have to implement two things for your FREContext class to be properly initialized.
The first one, of course, is the constructor. The second one is an implementation of getFunctions(): Read More
So you already know that, in order to make calls from your AIR app into native code, you need an Extension Context. One of the Extension Context roles is to tell AIR what native functionality is available for calling from ActionScript and this happens during the Extension Context initialization. This post will show you how this is done in C - you can use that in your C, C++ or Objective-C code. Read More
Do you remember the first call AIR makes when your AIR Native Extension is loaded in memory?
It's not a test. I'll even let you have a sneak peek, in case you've forgotten: when your ANE is first loaded, AIR calls its Extension Initializer: have a peek at what it looks like in C and in Java. Shortly after that the Extension Context is created. Read More
