Flash® Catalyst™ CS5 Bible

Foreword

In October of 2007, I was sitting in a conference room with members of my team at the interactive agency I worked at. We had been asked if we were interested in meeting with some people from Adobe on some possible features for what was at the time called Flex Builder.

The timing was great because we had recently launched a pretty sophisticated Flex Web application for a car manufacturer, and we had pushed Flex Builder and the Flex framework to its limits. We were thrilled with an opportunity to present all of the issues we had to the team to hopefully work on in the next version.

We sat in the room and dimmed the lights, and the team's product manager, Steve Heintz, made a clarification on the presentation. We weren't going to see Flex Builder, but an entirely new concept codenamed Thermo. As we watched the presentation, the team showed features for this mythical application including:

• Converting artwork into components without needing to go through the laborious skinning workflow.

• Editing designs in Illustrator within context of the Flex application.

• Rigging interactions between components.

• Capturing user interactions without needing to understand Flex.

• Working with design-time data to build data lists and components.

• And all this while writing MXML and ActionScript using the Flex framework behind the scenes.

We were floored, but at the same time were very skeptical — an application like Thermo was exactly what we needed for our recent project where we had a separate team of designers ...