Sun 7 Oct 2007
Frequently Questioned Answers about Thermo
Posted by Narciso Jaramillo under design | development | Flex | Thermo5 Comments
Well, Thermo caused quite a buzz at MAX, and needless to say, we’re very excited about all the reaction. If you weren’t at MAX, you can see Aral Balkan’s video of the Thermo demo up on YouTube: part 1, part 2, part 3.
Since we did the demo, I’ve been semi-obsessively searching MXNA for blog posts about Thermo, and among the generally positive responses, people have also posted a number of questions and concerns. I thought I’d address some of these here, to help clarify and amplify what we showed in the demo. (Sorry–no spoilers about release dates or other features here!)
The demo showed Thermo creating a lot of bitmap graphics. Will Thermo applications be large and bitmap-heavy?
The demo happened to have a lot of bitmaps in it, since it was a CD cover browser, but Thermo will work with both vector and bitmap assets. The main difference between graphics in Thermo and in Flex today is that vector artwork in Thermo is expressed through bona-fide MXML tags, rather than opaque SWF symbols. In the demo, for example, Photoshop text layers came over as TextGraphic tags, and rectangle shape layers came over as Rect tags. Naturally, MXML graphics will also support complex Bezier paths, rounded rectangles, and so on, and will support importing from Illustrator and Fireworks as well as Photoshop.
Why is it useful to have graphics tags? Why not just import graphics as SWFs or bitmaps as in earlier versions of Flex?
For static graphics, you could argue it’s about the same. But few graphics in a Flex application are static. Much of the “rich” in RIAs comes from dynamic graphics–graphics that change in response to user gestures or dynamic data.
In Flex as it is today, developers have to create dynamic graphics by writing imperative ActionScript code. With MXML graphics, developers no longer need to recode the designer’s graphics in order to make them dynamic–they can simply modify the graphics at runtime through simple property access, data binding, the transitions/effects engine, and so on. Designers can continue to edit the graphics visually in Thermo without disturbing the developer’s code.
For example, suppose I draw a button skin in Illustrator that’s filled with a blue gradient, and we want to create multiple buttons with the same look but different colors. My developer can just import that as MXML, and then data-bind the gradient color to some style parameter. Voila–instant styleable skin, without writing a line of AS code. I can then edit the shape of the skin visually in Thermo, and the color style will continue to work, without my having to rewrite a bunch of Graphics method calls.
Now let’s say I want to animate that gradient color when I mouse over the button. Again, I can create this through declarative transitions written in MXML, rather than having to build the animation into an opaque SWF symbol. And again, because the transition is in MXML rather than ActionScript code, I can visually design that transition using the Thermo UI.
The text field that was created in the demo seemed to have its skin specified inline. Will Thermo create large single-file applications? Will the code be huge?
Thermo is being created for designers, but of course it won’t be successful unless its output can be easily consumed by developers. Thermo will definitely provide easy ways to factor the resulting code into separate files. For example, skins can be automatically put into separate output files and generalized into CSS rules. (Flex Builder 3 actually already has functionality for extracting inline styles into CSS, and we would certainly have the same functionality in Thermo.)
One example of code factoring that wasn’t obvious from the demo was that when Steven created a list from the individual CD covers, the item renderer for the list was actually created as a separate file. When he then double-clicked on an item in the list to edit it, it felt like it was being edited directly in place in the context of the larger application, but Thermo was actually making edits to the separate item renderer file behind the scenes. This is an example of how we can keep clean code separation without forcing the designer to understand the guts of Flex.
It’s great that you can turn graphics into buttons, scrollbars, etc., but what about custom components? Will Thermo work with components created by developers?
Definitely. Our intention is to make it so that developers can create components that are usable in Thermo the same way the built-in components are. Naturally, they will need to conform to certain rules and/or implement a certain API in order for those components to work well in Thermo, but our intent is to keep those requirements lightweight.
Thermo seems geared towards letting designers build a complete Flex application. Does that mean you expect designers to create business logic as well?
That’s not the goal of Thermo. One way I like to think about the designer/developer dichotomy (woo, alliteration!) was suggested by Rob Adams: developers deal with system logic, and designers deal with user logic. The two are not exactly the same, though they obviously intersect. Our goal is to make it so that designers can use Thermo to design the user logic of the application (along with importing and editing the visual design), and provide a clean way for that user logic to be hooked up to backend data and business logic by a developer.
That’s all for now. Please feel free to comment (or post in your own blogs) if you have more questions about Thermo–naturally, we can’t answer all of them at this point, but we’re really interested to hear your thoughts!
digg this |
del.icio.us | 5 Comments
Some bumps…
Some bumps: Tinic Uro helped me understand the Hydra initiative… Narciso Jaramillo made Thermo a lot clearer for me. (I’m also happy about the ambient computing being done by Fernando Florez, and agree with Dan Florio on the serendipity of conferenc…
[…] “Well,” you may be saying, “Thermo looks great and all, but what do I do in the meantime?” The good news is that we have some nice improvements coming in Flex Builder 3 that help improve the visual design workflow, and you can try them out in the Flex Builder 3 beta that we posted to Adobe Labs last week. […]
“Our goal is *not* that a designer would build a complete app, with business logic and back-end integration, using Thermo. Conversely, our goal is *not* that a designer would build a toy prototype which would have to be completely torn apart and rebuilt by a developer.
Instead, our goal is that Thermo will allow the designer to create and own the portion of the app that s/he cares about–the visual design, the interaction design, and the user flow–and have that flow directly into production, where the developer can implement custom functionality, attach real back-end data, and hook up business logic.
In order for us to be successful at this, we obviously realize that the code Thermo generates has to be usable by a developer. Part of this will just be us being careful about making sure Thermo organizes and separates out code automatically to keep it clean without the designer having to worry about it too much.:”
It need to be able to output all the skins as AS and external classes. As devs nows how we right the stuff, and that how the Flex team wrote the stuff. If not we’ll only be spening time externalizing all the inline code. So for a ScrollBar for instance I would expect 4 classes, and please in AS, not MXML.
[…] There’s a really interesting discussion getting kicked around the blogosphere right now about this very topic on Grant Skinner’s blog, with a response/clarification at Rictus. […]
[…] Thermo is hiring, and one of our first job openings is for someone to help us create a next-generation learning experience. We want to make it easy for designers to get up to speed on Thermo quickly, and we’re going to need to communicate Thermo’s concepts through traditional written documentation, videos, animations, smoke signals, and however else we can convey them. […]