The second day MAX Chicago keynote just revealed “Thermo”, an upcoming Adobe product that makes it easy for designers to create rich Internet application UIs. Thermo allows designers to build on familiar workflows to visually create working applications that easily flow into production and development.
Features[list][*]Use drawing tools to create original graphics, wireframe an application design, or manipulate artwork imported from Adobe Creative Suite tools.
[*]Turn artwork from Adobe Photoshop, Illustrator, or Fireworks directly into functional components that use the original artwork as a “skin”.
[*]Define and wire up interactive behavior, such as what to do when a user clicks on something, without having to write code.
[*]Easily design UIs that work with dynamic data, such as a list of contacts or product information, without having access to the actual data source. Design-time sample data can be used as a realistic placeholder when laying out an application, testing interactivity, and choreographing motion. [/list]
Applications created in Thermo are Flex applications that can be loaded directly into Flex Builder, providing a great roundtrip workflow for designers collaborating with developers. The designer’s work can be incorporated directly into the production application with no loss of fidelity, and designers can continue to refine the design throughout the iterative development process.
More info & screenshots: http://labs.adobe.com/wiki/index.php/Thermo
coldFUSED
Yeh I am not sure about this one. First thing that comes to mind is “Adobe Go-Live”. I smell about 6 pounds of $hit.
Why 6 pounds you ask? Take the code created from an Adobe Go-Live website, print it out, you have six pounds of dead tree. Did I mention all of that was for a image rollover?
- 03 October 2007 01:44 AM
-
njadbe
@coldFUSED: We definitely hear you 
One of our main concerns is to make sure that the code Thermo creates works for developers. I used to work on HTML authoring tools, so I’m pretty familiar with the difficulty of clean code generation. One thing that makes it more tractable for us is that unlike HTML, we control the language and framework.
On that note, Ely Greenfield, the Flex architect, gave a great talk at MAX discussing some of the ways we’re planning to refactor the Flex framework to make skinning much more flexible. By having a cleaner separation between the presentation and the underlying controller logic and data for each component, we can actually make it so the designer can really own the design of the presentational aspects without affecting the code the developer needs to work on.
Thanks,
nj
Adobe Flex team
- 03 October 2007 07:28 PM
-
- Log in or join for free to make a comment.
