Posts tagged "AIR"

Contest for improving US government websites

Use your programming skills and web design know-how to help the US government improve its websites!

Adobe is a platinum sponsor for a contest called Design for America. The goal of the contest is to show government agencies better ways to present information to the public. Winners get cash awards and will have their entries showcased at the Gov 2.0 Expo in May in Washington, DC.

For details, visit this site:

http://blogs.adobe.com/adobeingovernment/2010/03/design_for_america.html

The importance of providing an update mechanism in an AIR application

Applications provide updates for many reasons, including bug fixes, security patches, and new functionality. This holds true for AIR applications as well.

Adobe ships occasional update versions of Adobe AIR. And Adobe AIR applications can take advantage of new features and bug fixes in new versions of the runtime.

Also, new versions of Adobe AIR may include updated versions of WebKit (the HTML rendering engine in AIR). This may change the behavior or appearance of HTML content in an AIR application. For example, improvements or corrections in WebKit may change the layout of HTML elements in an AIR application’s user interface.

It is important to provide an update mechanism in your application. When you update your application, the application can inform the user of the new update version. Should you need to update your application due to a change in the WebKit version included in AIR, the update mechanism will let your users know about the new version of your application.

AIR includes a update framework, which simplifies the task of managing update versions and adding appropriate user interface in your AIR application.

For more information, see “Updating AIR applications” in the AIR developer’s guides:

Also, these “Quick Start” sample applications show how to use the update framework:

AIR 1.5.1 doc updates

AIR 1.5.1 was released on 2/24/09. Although it was a minor release, there were a few enhancements that you should be aware of.

New event that indicates if the application was launched manually by the user or automatically at login

The InvokeEventReason class (in the flash.desktop package) defines the two possible string values for the InvokeEvent.reason property. InvokeEventReason.LOGIN defines the login case; InvokeEventReason.STANDARD defines the standard case.

Jeff Swartz wrote a new quick start to explain how to use this new functionality.

New property to return processor architecture

This new property (Capabilities.cpuArchitecture in flash.system) returns the processor architecture of the machine, as a string (such as “PowerPC” or “x86″).

Using these new APIs

If you want to take advantage of these new AIR 1.5.1 APIs, update your application descriptor to use the 1.5.1 namespace:

xmlns="http://ns.adobe.com/air/application/1.5.1"

If you do not need to use these new APIs, you do not need to update your application descriptor. Your application will be able to run with AIR 1.5.1 when the user updates the version of the runtime installed on their system.

You can find all the current AIR docs here: Adobe AIR resources