Sure a-lot has already been posted on this and I’m not going to beat a dead horse, but I will say that Adobe knows how to throw a party. From the individual classes to the general session to the after hours guitar hero, poker tables, Segueway race course and just providing a place to plug [...]
Sure a-lot has already been posted on this and I’m not going to beat a dead horse, but I will say that Adobe knows how to throw a party. From the individual classes to the general session to the after hours guitar hero, poker tables, Segueway race course and just providing a place to plug in your laptop and hang with other developers, they did it right.
Once of the most exciting things that I saw was a project code-named "Thermo" which is sort of like a WYSIWYG on steroids for Flex applications.
Let’s say you have a team of developers and a designer. The designer can take his/her Photoshop or Illustrator file and import it into Thermo, from there they can turn there designed elements into actual functioning application elements.
On the backend this is writing mxml that can be handed off to a developer in order to connect it to a database or do some more advanced coding with it.
Simply an awesome technology, but it begs the question, should designers be given that much power?
I know a few designers who could handle that, but there are some that I’ve worked with in the past that whom I wouldn’t even tell this application exists.
For more about Thermo check out it’s entry on the Adobe Labs Wiki
Leave Your Response