Comments on: Frequently Questioned Answers about Thermo

By: much ado about something » Want to help us create Thermo’s learning experience?

Tue, 12 Feb 2008 19:13:43 +0000

[...] 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. [...]

By: insidethebox » Thermo for design/dev workflow

insidethebox » Thermo for design/dev workflow — Fri, 09 Nov 2007 23:59:12 +0000

[...] 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. [...]

By: Tink

Tink — Thu, 11 Oct 2007 09:55:31 +0000

“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.

By: much ado about something » Design workflow features in Flex Builder 3

much ado about something » Design workflow features in Flex Builder 3 — Tue, 09 Oct 2007 03:30:57 +0000

[...] “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. [...]

By: JD on EP

JD on EP — Sun, 07 Oct 2007 15:01:51 +0000

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…