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
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
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
