This is part 4 of our Windows ANE tutorial which walks you through making an Adobe AIR Native Extension for Windows. At the end of this part you will have: An Adobe AIR Native Extension (ANE) ready to be used on Windows. Time 10-15 minutes Share on: WhatsApp Read More
At the end of this part you will have: A Windows DLL, ready to communicate with ActionScript and to be packaged in an ANE. Time 10-15 miutes Share on: WhatsApp Read More
At the end of this part you will have: A C/C++ project which you have set up to use the Adobe AIR C API. Note that, although the steps here are done with Microsoft Visual C++, you don’t necessarily need to stick with it. Any IDE or command-line compiler that builds C/C++ code will do, for example GCC. The most important steps in this part of the tutorial are making sure that your C/C++ code can see FlashRuntimeExtensions.h and link with FlashRuntimeExtensions.lib from the Adobe AIR SDK. Time 8-10 miutes Share on: WhatsApp Read More
We sometimes get asked for help with putting ANEs for Windows together, build automation and debugging. The inspiration for this tutorial came from Eric Zwar, who bought our eBook Easy Native Extensions, which has examples for iOS, and heroically applied its principles to making an AIR Native Extension for Windows. Thank you, Eric! I hope you like this one. Share on: WhatsApp Read More
When you make a native extension using the AIR C API, your native code tends to have two parts:
Ideally you want to keep the dependency between these two parts one-directional: the AIR-concerned part should depend on the functional part, but the functional part should not know about and depend on AIR. If you decide to reuse your, say camera or speech recognition functionality, in another project that's not AIR-related , you don't want to force that to include the AIR C API.
So, what happens if you need to dispatch an event from the functional part of your code? Say, the camera refused to start or the speech processor is ready with results and you want you alert AIR to this... Read More
The Extension Initializer and Finalizer are the entry and exit points to your native extension. They are also two of the ingredients that make your extension known to the world and make it distinguishable from other extensions in an app. This is why they need to have unique names. Their signatures however need to be exactly as prescribed by AIR. Today we look at what these are in the AIR C API.
Read MoreSo, you know what an AIR Native Extension (ANE) is and how it fits in your app. Next, you are contemplating an AIR Native Extension for Windows, while everyone is going crazy about iOS and Android. Read More
This is the title article for a series of posts that take a look into the components you'll need, in order to make a native extension for four different platforms. Read More
Before we define what Adobe AIR Native Extensions (ANEs) are, let us first marvel at Adobe AIR for a bit, starting with what it can do for you. Then we will move on to what it can't do for you. That's where it gets interesting and where ANEs come in. Read More
