The idea is that Thermo would not corrupt any code from the file that it is working on because we want designers and developers to be able to work on the same files. But obviously as you get deeper into development it may be that a designer has to be a little more careful as they make modifications since there will now be dynamic code dependent on the UI. But we're very early here so as we build the product out we'll want to test these kinds of scenarios very carefully.
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of hank williams Sent: Thursday, October 04, 2007 2:13 PM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] Thermo & Cairngorm Yeah, thats why my initial post said "Do any adobe folks know whether..." :) Hank On 10/4/07, Merrill, Jason < [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > wrote: I don't think anyone knows the answer to that yet (at least from the Max demo) - except Adobe people and a few Adobe insiders. Jason Merrill Bank of America GT&O Learning & Leadership Development eTools & Multimedia Team ________________________________ From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of hank williams Sent: Thursday, October 04, 2007 4:58 PM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] Thermo & Cairngorm Hmmm... Thanks Jason, but I am not sure you quite got the gist of my question. Perhaps I was unclear. I was under no illusion that one would be creating business logic in Thermo. My question is whether the workflow between caringorm delegates, commands, etc and the Thermo UI code will be easily maintained separately. Will we be able to embed cairngorm commands and model access in the UI stuff that is generated by Thermo. Will the round-tripping work. Does the conceived work flow target the cairngorm developer along side the designer in a smooth way. Hank On 10/4/07, Merrill, Jason <[EMAIL PROTECTED]> wrote: 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: flexcoders@yahoogroups.com [mailto: flexcoders@ <mailto:flexcoders@> yahoogroups.com] On Behalf Of Paul Andrews Sent: Thursday, October 04, 2007 7:46 AM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] Thermo & Cairngorm ----- Original Message ----- From: "hank williams" <[EMAIL PROTECTED] <mailto:hank777%40gmail.com> > To: < flexcoders@yahoogroups.com <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
