Apache Adobe Flex TutorialTutoriaux Adobe Flex & AIR en Français

Adobe Air 2.0 et Flash Player 10 en beta sur Adobe Labs

Si vous suivez les Adobe Feeds sur Flex, vous n'avez pas pu rater la nouvelle du jour. Les produits Adobe les plus attendus depuis Adobe Max 2009 (Los Angeles) sont sortis en béta sur les Adobe Labs. Vous trouverez donc sur les Adobe Labs:

• Adobe AIR 2 beta
• Flash Player 10.1 prerelease (Windows, Mac et Linux)

Notez bien qu'il faut prendre ces versions avec des pincettes et surtout ne pas les intégrer en environnement de production car elles sont susceptibles de changer d'ici la version finale.

Les fonctionnalités attendues

Voici un récapitulatif des fonctionnalités annoncées à Adobe Max:

• Adobe Air 2.0, les fonctionnalités annoncées
• Flash Player 10.1, des améliorations majeures

Ce sont des versions beta, toutes les fonctionnalités ne sont pas encore au rendez-vous (les versions finales sont prévues pour début d'année vraisemblablement).

Installation de Flash Player 10.1 prerelease et fonctionnalités manquantes

D'après les release notes, voici les fonctionnalités qui ne sont pas encore présentes:

Global error handler support

Support for the global error handler will be available in a future beta refresh of Flash Player 10.1.

Macintosh PowerPC support

Support for the Macintosh PowerPC platform is not available in this prerelease but will be available in a future prerelease.

GPU compositing (desktop platforms only)

Hardware compositing (wmode=gpu) has been disabled on desktop platforms only. Hardware compositing

in Flash Player 10 improves performance in select cases, but it can decrease performance in others. In addition, driver support varies widely on desktops. Given these complications, Flash Player 10.1 will ignore the wmode=gpu embed parameter and composite graphics in software.

H.264 video hardware decoding

NVIDIA ION (MCP79) and GeForce 8400GS (G98) GPUs: Video clips with unusual horizontal resolutions may not be GPU-accelerated on these particular video cards in this beta release. On these cards, playing videos with such resolutions will force playback via software decoding. The most likely place you will encounter this problem is with YouTube videos which have an “HQ” button. Activating that button will display a higher resolution version of the video which is 854 pixels in width. These cards currently do not support that width, and Flash Player will default to normal software decoding for these clips. As a workaround, append “&fmt=22” to the end of the YouTube video clip URL. This will play the video in HD mode (with a width of 1280 pixels), which is supported by these cards. This known issue will be fixed with an updated NVIDIA driver or Flash Player 10.1 release.
In Flash Player 10.1, H.264 hardware acceleration is not supported under Linux and Mac OS. Linux currently lacks a developed standard API that supports H.264 hardware video decoding, and Mac OS X does not expose access to the required APIs. We will continue to evaluate adding the feature to Linux and Mac OS in future releases.

Other

• Clipboard keyboard shortcuts don't function in Safari 3 and Safari 4. (2472648)
• If a socket you are using times out, Flash Player may crash when attempting to use it again. To work around this, delete any Socket after a connection attempt times out.
• Flash Player installers running on Windows Vista will display a duplicate dialog box asking users confirm running content that was downloaded from the Internet.

Instructions d'installation pour Adobe Air 2 beta SDK et fonctionnalités manquantes

Adobe a mis à jour la FAQ pour l'installation du SDK 2.0beta d'Air: How to overlay the Adobe AIR SDK for use with the Flex SDK. Vous trouverez aussi la liste des fonctionnalités qui ne sont pas encore activées dans cette beta:

• The Adobe AIR install badge cannot be used to deploy an AIR 2 application through a web page. This functionality will be supported in the shipping version of AIR 2.
• Backward compatibility issues

  We have had reports of some backward compatibility issues. Please report any issues you find when using or building existing AIR applications. Such issues may include applications not displaying UI, not functioning correctly, or crashing. Issues have been reported for Acrobat.com, eBay Desktop, Times Reader, Adobe Media Player, DestroyTwitter, FOX News Live, AOL Top 100 , Drag'n share, AdobeDirectory, Yammer.

• Screen reader support
  • Support for top-level activation and automatic announcement of a screen's contents is not complete.
  • Screen reader support is not available for HTML-based applications or the HTMLloader control. While screen reader support for HTML-based applications is not planned for AIR 2, we do plan to add this feature in a future release.
• DRM APIs
  • The DRM APIs are currently disabled and will be re-enabled in the final release.
• Microphone access API
  • Testing of this feature has been limited, especially around simultaneous local access and NetStream recording.
  • Documentation for this feature is incomplete.
• Use of ApplicationUpdaterUI in Flex4 applications
  • AIR 2 SDK comes with a new ApplicationUpdater UI lib targeted for Flex 4 applications (applicationupdater_ui4.swc) besides the existing one targeted for Flex3 applications (applicationupdater_ui.swc). By default, Flex Builder 3 includes both of them in AIR projects, so the Flex3 version of the library might get used instead of the right one. In order to avoid problems, be sure to remove the unused version library from the list of linked libraries in your project via Project properties > Flex build path > Library path.
• NativeProcess API
  • On Linux, it is not currently possible to read more than 4096 bytes from the standard output stream of a process launched by an AIR application.

Mettre à jour votre application Adobe Air pour AIR 2

Si vous voulez utiliser Adobe Air 2.0 beta, il vous suffit de mettre à jour votre SDK Air. Mais n'oubliez pas de modifier la version d'Adobe Air dans le descripteur XML de votre application. Si vous oubliez cette étape, l'application se lancera mais va crasher quand vous tenterez d'utiliser une nouvelle classe de la beta. Voici un tutorial qui expliquait cette manipulation pour le passage de Air 1.1 à Air 1.5. Modifier le avec la valeur "2.0beta".