Do you remember the three ways that native code can send data back to ActionScript? Here they are for a quick revision:
- Returning a FREResult object from a call to FREFunction.
- Using output parameters in a FREFunction.
- Sending an event to ActionScript.
We have mentioned the Extension Context a few times already:
I reckon it's time to look at what actually an Extension Context is. Agreed? 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 More
If you've ended up on this page, you are probably already familiar with what goes into an ANE for iOS and an ANE for Mac OS. You also know that one of the main ingredients for these is the AIR SDK and its interface for these two platforms: the AIR C API.
Now, when you try to include that in your iOS or Mac OS native library, Xcode helpfully asks you whether you want the API's header file, FlashRuntimeExtensions.h, copied into your project. What should you do?
We have so far established what you need to set in a native extension, in order for it to be distinguishable from other native extensions when used in an app. We also saw that you need to set that in the extension descriptor file.
Now let's have a look at how a native extension is used in an app and what you need to set in the app to help AIR find and load the native extension. Read More
In yesterday's article , Preparing an ANE to be used in an app, we established that your ANE needs:
- an Extension ID;
- Extension Initializer and Finalizer.
We also saw where these go: in the extension descriptor file. Now's the time to see what that file exactly is. Read More