Adobe AIR 1.5.3 and Flash Player 10.0.42

Following the AIR 2 and Flash Player 10.1 betas last month, comes updates for the current platform runtimes in the form of AIR 1.5.3 and Flash Player 10.0.42.

Most important to my work is the Publisher ID changes in AIR. I’ve have the need to migrate certificates before, so have paid close attention to the changes as outlined by Oliver Goldman. Hopefully, these changes will make things more direct when having to migrate code signing certificates for our apps using a non-computed Publisher ID.

While these are minor updates to end-users, it’s important to note that Adobe does update the platform runtimes a number of times each year to address bugs and small feature enhancements. They do take good care of their platform and their users!

Adobe AIR 1.5.3 Release Notes

Adobe AIR Team blog post announcing AIR 1.5.3

Flash Player 10.1 and AIR 2.0 Public Betas

The Flash Player 10.1 and AIR 2.0 Public betas are now available via Adobe Labs:

Flash
Flash Player 10.1

AIR
AIR 2.0

These are the first fruits to come out of the Open Screen Project – and hopefully much more good will follow as FP 10.1 for mobile devices will begin shipping later this year into next covering mobile platforms like Palm, Blackberry, and Android.

Some good resources:
Flash Player 10.1 Beta Release Notes
Introducing Adobe AIR 2 beta
Flash Player 10.1 public prerelease demos and interviews
Mobile and digital home

UPDATE: Wow. Christian Cantrell has everything you could need at AIR 2 Public Beta Resources.

Flash Builder: Wrong Debug Player!

Every once in a while, Flash Builder loses its mind when I attempt to debug a project and tells me that I don’t have a debug version of Flash Player on my machine. I do… FB is just crazy. Right.

Debug
Sometimes it’s looking at the player running in the browser, in which case I just need to perform a debug player install from:
http://www.adobe.com/support/flashplayer/downloads.html

Other times, it’ll be pissed off about the player used by Flash Professional at:
C:\Program Files (x86)\Adobe\Adobe Flash CS4\Players

I’ve found a pretty foolproof (for me) way to fix this secondary problem. Just grab FlashPlayer.exe from:
C:\Program Files (x86)\Adobe\Adobe Flash Builder {such and such release}\player\win

Copy this into the Flash Pro location, restart FB, and you should be good.

Don’t know why this happens from time to time… but it’s happened enough that I feel the need to document it- at least for myself.

Scaling Your Images in Flash Player? Smooth Those Things!!!

I actually forgot to apply the “smoothing” property to a flash.display.Bitmap display object being scaled inside Flash Player. Just look at the difference such an oversight made!

Smoothing

Since I was using a flash.display.Loader display object to load the image up, and Loader has no smoothing property, I totally spaced on this and it’s been out there for months rendering images in a pretty crappy way. I just needed to assign the image data to a Bitmap object and use that for display instead.

1
2
3
4
5
6
private function imageLoaded(e:Event):void {
    var imageBitmap:Bitmap = imageLoader.content as Bitmap;
    imageBitmap.smoothing = true;
    imageDrag.addChild(imageBitmap);
    //scale away!
}

Easy.

Learn from my blunder- always make sure to enable smoothing!

Flash Player 10 Security Issue Resolution

I had posted earlier concerning a strange issue with Flash Player 10 where the SWF would refuse to load if being served over a Java servlet.  We’ve been able to resolve the issue by explicitly transferring any SWF content with a “Content-Disposition” header of “inline” as suggested by Adobe.  The relevant portion of this document is replicated below:

Starting with version 10,0,2, if Flash Player sees a “Content-Disposition: attachment” header while downloading a SWF file, it will ignore the SWF file rather than play it. Note that this restriction applies only to SWF files and not to other types of content, such as images, sounds, text, or XML files, policy files, etc.

If you control the HTTP server on which the SWF file resides, determine whether you trust the SWF file to execute in the server’s domain. If so, remove the “Content-Disposition: attachment” header by changing your HTTP server’s configuration.

While our resolution did differ slightly from the one posted above.  It effectively does the same thing.