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
Do you remember when we talked about what an Extension Initializer and Finalizer are and what happens if they don't have unique names? We also saw what they look like in C. Today we are contrasting that with their Java versions. 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 MoreIf 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:
We also saw where these go: in the extension descriptor file. Now's the time to see what that file exactly is. Read More
The other week we had an overview of how an AIR Native Extension (ANE) fits in your app, after which we saw what goes into an ANE. We even inspected the elements of an ANE for:
Today we are zooming in to see what you need to set in the ANE, so that an app can find it. Read More
When you make a native extension, you'll find that the communication between ActionScript and native code is somewhat lopsided.
Read MoreSo you are an Android guy. Or gal. Or, you are an ActionScript person, who wants to expand to Android. Same difference. Here is a bit of prerequisite information, in case you need it:
Next, let us see the ingredients that you have to provide for an ANE and those that are provided for you. You will have to make two libraries: Read MoreWe saw what an AIR Native Extension (ANE) is and how it fits in your app. Now let us zoom in and see what's under the hood of an ANE for iOS. There are two main components that you need to provide, in order to make an ANE for iOS Read More
