When you develop a native extension for an AIR for TV device,
do the following iterative tasks:
-
Write the native implementation.
For more information,
see
Coding the native side with C
.
-
Write the real ActionScript implementation.
For more
information, see
Coding the ActionScript side
. Be sure to consider
Native extension backward compatibility
.
-
Write the stub ActionScript implementation, and optionally
write a simulator ActionScript implementation.
For more information,
see
The device-bundled extension and the stub extension
and
Check for extension support
.
-
Create a certificate for signing your native extension. This
step is optional.
For
more information, see
Creating a signed certificate for a native extension
.
-
Build the device-bundled extension and the stub extension
by using the AIR for TV make utility. This process creates a ZIP
file to install the device-bundled extension on the device. It also
creates an ANE file of the stub extension for an AIR application
to build and test with.
For more information, see
Building an AIR for TV native extension
.
-
If a simulator ActionScript implementation is available,
build the simulator extension by using the AIR for TV make utility.
This process creates an ANE file for an AIR application to build
and test with.
For more information, see
Building an AIR for TV native extension
.
-
Add any required resources, such as images, to the ZIP file
and ANE file.
For more information, see
Adding resources to your AIR for TV native extension
.
-
Test the simulator extension on a desktop computer.
For
more information, see
Debugging AIR for TV applications
.
-
Install the device-bundled extension on the device.
For
more information, see
Installing the device-bundled extension on the AIR for TV device
.
-
Test the device-bundled extension on the device.
For
more information, see
Running an AIR application on an AIR for TV device
and
Debugging AIR for TV applications
.
-
Deliver the stub or simulator ANE files, or both, to application
developers.
|
|
|