Flex

The Open Web: Now Sexier and Smaller

In the past Open Web proponents have criticized Flash and Flex because the SWF specification - while being published and publicly available - limited what readers could do with the specification. More specifically the agreement to view the specification required that readers not build programs that would run SWF files. The intentions behind this were good - Adobe does not want Flash to have inconsistent and incompatible implementations.

Today Adobe Systems has announced that they are removing those restrictions on the SWF and FLV specifications! This is very exciting news and something I’ve been lobbying for since I started working for Macromedia (actually I think I began bugging Emmy Huang about this before I started working for Macromedia). Flash has become the standard for sexier web experiences with RIAs, video on the web, and interactive web content. Today that standard is truly open!

Count on Flex – 326

326 = Number of Flex applications in the Flex.org Showcase.

Many Flex applications either require authentication or are behind firewalls. However the Flex.org Showcase lists publicly available Flex applications. If your Flex application is not listed, go add it today!

That’s 326 more reasons you can Count on Flex!

“Count on Flex” is a series of blogs about the current state of the Flex ecosystem… by the numbers.

Count on Flex – 1,117,019

1,117,019 = Number of Lines of Open Source code for Flex, BlazeDS, and Tamarin.

200,897 lines in the flex_sdk

218,789 lines in blazeds

353,644 lines in tamarin-central

343,689 lines in tamarin-tracing

That’s 1,117,019 more reasons you can Count on Flex!

“Count on Flex” is a series of blogs about the current state of the Flex ecosystem… by the numbers.


For this post I did a very basic calculation which doesn’t factor out comments and licenses. For the Flex SDK and BlazeDS I used this command:

JavaOne 2008 Festivities

JavaOne 2008 begins in just over a week! Adobe is a sponsor again so you will find me in the booth when I’m not out at the many JavaOne parties. On Wednesday night Adobe will be hosting their party at Jillian’s. Preceding the party Chet Haase and I will be presenting a quick, fun session about Flex. More details at http://flex.org/javaone

Also on Monday at CommunityOne I’ll be doing a Lightning Talk and participating in a panel.

Talkin’ About a Revolution

Revolutions may be enabled by technology, but they are driven by people. Adobe’s recent announcements about Flex, Flash, and Adobe AIR on Linux are the most recent technology enablers for the software revolution that is currently underway.

Usually I’m one of the first to post about Adobe’s Linux related announcements. My trip to Bangalore, India, however, made me a little late to the party this time. In case you haven’t seen the announcements, on March 31, 2008 Adobe released an alpha version of Adobe AIR on Linux and an update to the alpha version of Flex Builder 3 for Linux (which supports building AIR applications on Linux). On the same day Adobe also announced that we joined the Linux Foundation.

Flex 3 Skin Transitions with Degrafa and AnimateColor

It is always fun when you discover new product features that you never knew existed. This happened to me last week as I was looking into Flex 3 skinning. It turns out that not only can you use a single class with states to define component skin states (like “up”, “down”, and “over” on a Button) but transitions also work with these skins! This feature has been noticed by others as well. But I figured I’d blog about it anyways - because it’s so cool!

Video: Building Turbulent AIR Applications on Linux

Adobe recently released an alpha version of Adobe AIR for Linux and a updated alpha 3 version of Flex Builder for Linux. I wanted to show everyone how easy it is to build and run desktop RIAs with Flex and Adobe AIR so I recorded a quick video. In the video I use Papervision3D and a component I created called “TurbulentApplication” to turn an ordinary AIR Application into an application which pitches and rolls in response to the accelerometer values on my Ubuntu laptop. While most AIR applications work on Windows, Mac, and Linux, this one only works on Linux because as far as I know Windows and Mac don’t have a way to read the accelerometer values from a file, like Linux. If you have Linux (and an accelerometer) and want to run the application you can download it here. If you want to download the source code for the TurbulentApplication component, you can get it here.

Bursting Bubbles

Bubblemark is a popular benchmark for some of the RIA technologies including Flex, Adobe AIR, Ajax (DHTML), Java Swing, Java FX, Silverlight, etc. I’ve been trying for a while to create a new Flex version of Bubblemark to show just how fast Flash Player and Adobe AIR are. But I’ve come to a few realizations… First, you can make benchmarks say whatever you want them to say.

When trying to optimize Bubblemark I found a few interesting things. First was that IE (and some versions of Firefox) limit the frame rate of Flash Player (and possibly other plugins). This means that while the Flash Player VM might be able to actually achieve 200+ frames per second the actual visual result might be only 60 fps. And maybe this is for good reason. Why do you need a visual frame rate faster than the refresh rate on a monitor? You don’t. And especially not for RIAs.