This content has been marked as final. Show 3 replies
You can read about Thermo here:
It allows designers to create visual components using work done in Photoshop, Illustrator, etc., and hand them over to a Flex developer.
It's meant to help split the visual design and coding phases of a project.
"rtalton" <email@example.com> wrote in message
> You can read about Thermo here:
> It allows designers to create visual components using work done in
> Illustrator, etc., and hand them over to a Flex developer.
> It's meant to help split the visual design and coding phases of a project.
I think that's the opposite of what Adobe intends. It's meant to help
_unify_ the design and coding phases, to allow designers to take their
designs further down the path of interactivity without a hard core
I'm assuming the designer is not the coder... hence the split I see in assignments during project development.
Example: I'd love to have a designer help me by coming up with Flex UI components without having to write any code or use Flex at all. Just give me their beautiful design done outside of Flex )in Thermo) and I'll code the functionality. Where I work, at least, no designer wants anything to do with any kind of coding.