Building Adobe AIR Applications

More documents

Recommendations

Info

BUILDING ADOBE AIR APPLICATIONS Using native extensions for Adobe AIR Often, the same native extension targets multiple platforms. The extension’s ANE file contains ActionScript and native libraries for each supported platform. Usually, the ActionScript libraries have the same public interfaces for all the platforms. The native libraries are necessarily different. Sometimes a native extension supports a default platform. The default platform’s implementation has only ActionScript code, but no native code. If you package an application for a platform that the extension does not specifically support, the application uses the default implementation when it executes. For example, consider an extension that provides a feature that applies only to mobile devices. The extension can also provide a default implementation that a desktop application can use to simulate the feature. Supported device profiles The following AIR profiles support native extensions: extendedDesktop, starting in AIR 3.0 mobileDevice, starting in AIR 3.0 extendedMobileDevice, starting in AIR 3.0 More Help topics AIR profile support Task list for using a native extension To use a native extension in your application, do the following tasks: 1 Declare the extension in your application descriptor file. 2 Include the ANE file in your application’s library path. 3 Package the application. Declaring the extension in your application descriptor file All AIR applications have an application descriptor file. When an application uses a native extension, the application descriptor file includes an element. For example: com.example.Extension1 com.example.Extension2 The extensionID element has the same value as the id element in the extension descriptor file. The extension descriptor file is an XML file called extension.xml. It is packaged in the ANE file. You can use an archive extractor tool to look at the extension.xml file. Last updated 7/8/2013 143
BUILDING ADOBE AIR APPLICATIONS Using native extensions for Adobe AIR Including the ANE file in your application’s library path To compile an application that uses a native extension, include the ANE file in your library path. Using the ANE file with Flash Builder If your application uses a native extension, include the ANE file for the native extension in your library path. Then you can use Flash Builder to compile your ActionScript code. Do the following steps, which use Flash Builder 4.5.1: 1 Change the filename extension of the ANE file from .ane to .swc. This step is necessary so that Flash Builder can find the file. 2 Select Project > Properties on your Flash Builder project. 3 Select the Flex Build Path in the Properties dialog box. 4 In the Library Path tab, select Add SWC.... 5 Browse to the SWC file and select Open. 6 Select OK in the Add SWC... dialog box. The ANE file now appears in the Library Path tab in the Properties dialog box. 7 Expand the SWC file entry. Double-click Link Type to open the Library Path Item Options dialog box. 8 In the Library Path Item Options dialog box, change the Link Type to External. Now you can compile your application using, for example, Project > Build Project. Using the ANE file with Flash Professional If your application uses a native extension, include the ANE file for the native extension in your library path. Then you can use Flash Professional CS5.5 to compile your ActionScript code. Do the following: 1 Change the filename extension of the ANE file from .ane to .swc. This step is necessary so that Flash Professional can find the file. 2 Select File > ActionScript Settings on your FLA file. 3 Select the Library Path tab in the Advanced ActionScript 3.0 Settings dialog box. 4 Select the Browse To SWC File button. 5 Browse to the SWC file and select Open. The SWC file now appears in the Library Path tab in the Advanced ActionScript 3.0 Settings dialog box 6 With the SWC file selected, select the button Select Linkage Options For A Library. 7 In the Library Path Item Options dialog box, change the Link Type to External. Packaging an application that uses native extensions Use ADT to package an application that uses native extensions. You cannot package the application using Flash Professional CS5.5 or Flash Builder 4.5.1. Details about using ADT are at AIR Developer Tool (ADT). Last updated 7/8/2013 144
Page 1 and 2:
Building ADOBE ® AIR ® Applicatio
Page 3 and 4:
Contents Chapter 1: About Adobe AIR
Page 5 and 6:
BUILDING ADOBE AIR APPLICATIONS Con
Page 7 and 8:
BUILDING ADOBE AIR APPLICATIONS Abo
Page 9 and 10:
BUILDING ADOBE AIR APPLICATIONS Ado
Page 11 and 12:
Page 13 and 14:
BUILDING ADOBE AIR APPLICATIONS Wor
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Chapter 4: Adobe Flash Platform too
Page 23 and 24:
Page 25 and 26:
BUILDING ADOBE AIR APPLICATIONS Cre
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
BUILDING ADOBE AIR APPLICATIONS Dev
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Chapter 7: Developing AIR applicati
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98: BUILDING ADOBE AIR APPLICATIONS Dev
Page 147: BUILDING ADOBE AIR APPLICATIONS Usi
Page 151 and 152: BUILDING ADOBE AIR APPLICATIONS Usi
Page 153 and 154: BUILDING ADOBE AIR APPLICATIONS Act
Page 155 and 156: BUILDING ADOBE AIR APPLICATIONS Act
Page 157 and 158: BUILDING ADOBE AIR APPLICATIONS AIR
Page 161 and 162: Chapter 12: AIR Developer Tool (ADT
Page 185 and 186: BUILDING ADOBE AIR APPLICATIONS Sig
Page 199 and 200:
BUILDING ADOBE AIR APPLICATIONS AIR
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Chapter 15: Device profiles Adobe A
Page 239 and 240:
Page 241 and 242:
Chapter 16: AIR.SWF in-browser API
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
Chapter 17: Updating AIR applicatio
Page 251 and 252:
BUILDING ADOBE AIR APPLICATIONS Upd
Page 253 and 254:
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
Page 267 and 268:
Page 269 and 270:
BUILDING ADOBE AIR APPLICATIONS Vie
Page 271 and 272:
BUILDING ADOBE AIR APPLICATIONS Vie
Page 273 and 274:
BUILDING ADOBE AIR APPLICATIONS Deb
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
Page 281 and 282:
Page 283 and 284:
Chapter 20: Localizing AIR applicat
Page 285 and 286:
BUILDING ADOBE AIR APPLICATIONS Loc
Page 287 and 288:
Page 289 and 290:
Page 291 and 292:
Page 293 and 294:
Page 295 and 296:
BUILDING ADOBE AIR APPLICATIONS Pat
show all

Building Adobe AIR Applications

Create successful ePaper yourself

Delete template?

Save as template?