Why Thermo should matter to Flex developers

Submitted by Falken on

Two interesting posts over on the FlexCoders mailing list recently, related to Adobe's Thermo graphical design tool for Flex.

First up is Matt Chotin who says:

"Thermo ... means that we're going to be able to allow Flex Builder to become even more developer focused ... [this] means more ngineering effort behind the coding features"

This is doubleplus good news for the Linux beta version of Builder, which currently lacks several important features of the Windows and Mac version like refactoring.

Secondly there is Ely Greenfield who comments:

"I think the contract between the [Thermo using] designer and [Builder or SDK using] developer can be 90% captured as 'I need elements of these types with these ids, and other than that go to town.'"

This means it'll be very easy to intergrate Thermo made designs into applications, and not have to worry too much if the designer updates the layout.
If you've seen the Code Behind patten in Flex you'll know how this can work really well even without Thermo.

Sections