ANE in under an hour
At the end of this part you will have
- A Flex mobile app with placeholder functionality for showing preview from the native camera. Check this out If you are asking "Why Flex and not pure ActionScript?"
- The means to run and test your ANE as soon as you write its first lines of code - a much better option than tapping away blind.
- Understanding of the 'grand plan' behind the ANE.
Time15-20 minutes Continue Reading
At the end of this tutorial you will have
- A native extension for AIR that connects with the native camera and captures frames from it.
- A test app that uses the native extension and can help you test and debug its code.
Total timeI've broken down the tutorial into parts, each of which should take between 5 and 20 minutes to implement. I expect the full tutorial to take you between an hour and a half and two hours in total. You've got to love software project estimates. :) If you've completed the whole tutorial, leave a comment and let me know whether my estimate was way off base. Continue Reading
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. Continue Reading
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... Continue Reading
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. Continue Reading
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. Continue Reading
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:
- unloading can be triggered by one of three different things - have a look at 1a, 1b and 1c on the diagram below;
- there is no guarantee that an extension will be unloaded at all. Continue Reading
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: Continue Reading
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: Continue Reading