I was there for the Thermo demo (which was awesome), and they basically
said Thermo is for designing Flex apps and jump-starting the basic
interactivity between components - it's not going to be targeted at
doing the full-blown architecture/business logic/coding of am MXML app.
You can have a designer work with Thermo, while the developer works with
Flex.
Jason Merrill
Bank of America
GT&O Learning & Leadership Development
eTools & Multimedia Team
________________________________
From: [email protected]
[mailto:[EMAIL PROTECTED] On Behalf Of Paul Andrews
Sent: Thursday, October 04, 2007 7:46 AM
To: [email protected]
Subject: Re: [flexcoders] Thermo & Cairngorm
----- Original Message -----
From: "hank williams" <[EMAIL PROTECTED]
<mailto:hank777%40gmail.com> >
To: <[email protected]
<mailto:flexcoders%40yahoogroups.com> >
Sent: Thursday, October 04, 2007 12:39 PM
Subject: [flexcoders] Thermo & Cairngorm
> Do any adobe folks know whether thermo will easily support the
> cairngorm architecture? Ideally I would like to either replace
(or
> ideally enhance) my view classes with thermo and keep all by
business
> and communications logic exactly the same as it is now. Will
this
> "transition to Thermo" workflow be supported?
>
> Hank
From the videos, I would surmise that Thermo is a very nice
screen design
tool, but doesn't automatically include anything else besides
basic
interactions. You just need to add the other architectural
layers (as per
cairngorm) yourself. It really doesn't seem to affect business
and
communications logic at all.
I'm not sure what transition is required. It replaces aspects of
the current
flexbuilder design view and includes extra functionality and
intelligent
importation of graphical elements.
Paul
