But doesn't Thermo limit you to just Flex? I think that is a bad thing. I have had horrible experiences with Flex development. I would consider myself a fairly savvy at what I do. Like some, I can design a composite in Fireworks and then build the xhtml/css/javascript prototype. Thermo outputs mxml for flex. If I want to make an element do something I am at a loss as I do not know Flex or ActionScript well enough to do anything. I can find numerous amounts of ajax/js/css resources to build the interactions that I know are possible. 99% of the time I can create a UI composite in Fireworks and build the High Fidelity Prototype in no time.
To follow the article form the first post, Fireworks is an awesome tool for creating UI. I have used it for the last 8 years and have never been able to not do something that I needed. Grady On Jan 30, 2008 10:00 AM, Narciso Jaramillo <[EMAIL PROTECTED]> wrote: > Coming in on this thread a bit late...lots of good stuff here! > > David Malouf wrote: > > > The Thermo stuff is definitely interesting, but thinks like a graphic > > designer, not like an interactive designer. Expression in their > > tutorials anyway is thinking similarly. > > > Basic assumption that is false that both are making is that I'm going > > to make a finalized high fidelity graphic UI as a flat screen to start > and > > THEN add interactive elements. This goes against the very way IxD's > have > > been working. > > Just a quick note on this... Our current public Thermo demo does > emphasize the graphic-design-to-production workflow, but we're also > interested in the early-stage interaction design workflow. We do plan to > have basic drawing tools and built-in components to let you do > wireframing, and you can build custom components and try out > interactions and transitions in wireframe as well. > > It sounds like the overall message of this thread is that the > interaction design workflow is much more about early-stage > experimentation, screen architecture, and prototyping, and that while > visuals are somewhat important (for sketching and presentation > purposes), exact visual bits aren't. Is that a fair characterization? > > I'd definitely be curious to hear what other kinds of interaction design > needs aren't being addressed by visual-production-oriented design tools > today. > > By the way, I'm going to be at Interaction '08 along with other Thermo > folks from Adobe--if you see one of us, please stop us and have a chat! > > Thanks, > > Narciso (nj) Jaramillo > Adobe Thermo team > > ________________________________________________________________ > *Come to IxDA Interaction08 | Savannah* > February 8-10, 2008 in Savannah, GA, USA > Register today: http://interaction08.ixda.org/ > > ________________________________________________________________ > Welcome to the Interaction Design Association (IxDA)! > To post to this list ....... [EMAIL PROTECTED] > Unsubscribe ................ http://www.ixda.org/unsubscribe > List Guidelines ............ http://www.ixda.org/guidelines > List Help .................. http://www.ixda.org/help > ________________________________________________________________ *Come to IxDA Interaction08 | Savannah* February 8-10, 2008 in Savannah, GA, USA Register today: http://interaction08.ixda.org/ ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
