What goes into an AIR Native Extension?

Opt In Image
Early bird offer on the ANE eBooks

 

Buy any Easy Native Extensions 2nd Edition package and get our $99 iOS + Android ANE Template completely free before the end of June 2015.

 

 

  • step-by-step guide to making your iOS extension in under an hour
  • library for data conversion between ActionScript and native code
  • tutorials
  • infographics
  • code included

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.

Birds-eye view

In a nutshell, you need three components for an AIR Native extension. Two of them are made by you and the third one is provided by Adobe.

You need to provide (write) two libraries:

  • an AIR library, compiled as a .swf file;
  • a native  library, compiled either as an .a.jar , or .DLL file.

Adobe has provided the ‘glue’ for these two in the form of a native API that sits between your two libraries and translates ActionScript calls and data to native code and vice versa. It comes in two flavours:

  • AIR C API;
  • AIR Java API.

Which one is your platform?

The following posts let you zoom in and see what library format you will need for each platform:

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code class="" title="" data-url=""> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong> <pre class="" title="" data-url=""> <span class="" title="" data-url="">