Comments on: Adobe Thermo Rocks My World http://digitalstevenson.com/jeff/blog/archives/25 what happens in the inbetween Tue, 06 Jan 2009 13:44:07 +0000 http://wordpress.org/?v=2.5 By: The Intermission » Blog Archive » Adobe Thermo - Deserves a Second Mention http://digitalstevenson.com/jeff/blog/archives/25#comment-82 The Intermission » Blog Archive » Adobe Thermo - Deserves a Second Mention Wed, 31 Oct 2007 03:50:41 +0000 http://digitalstevenson.com/jeff/blog/archives/25#comment-82 [...] mentioned Adobe Thermo in an earlier post, but I recently found some more information that I thought was worth sharing. Peter Elst was able [...] […] mentioned Adobe Thermo in an earlier post, but I recently found some more information that I thought was worth sharing. Peter Elst was able […]

]]> By: GraeNormal http://digitalstevenson.com/jeff/blog/archives/25#comment-43 GraeNormal Thu, 04 Oct 2007 15:55:42 +0000 http://digitalstevenson.com/jeff/blog/archives/25#comment-43 What's wrong with a WYSIWYG? True, a lot of WYSIWYG page designers create horrible code, but there's no reason to assume that Thermo will too. Actually, I think Flex separates visual design from code so completely that the code isn't really affected by the visual design. I'm just speculating, but I think it works this way: 1. You create a visual design like you would in Photoshop or Fireworks. 2. You give the elements in the visual design an ID. Those IDs are compiled in an XML document. 3. The code describes what to do with those elements in the XML document. That means you could move the visual elements anywhere you want and style them any way you want without really affecting the code. What’s wrong with a WYSIWYG? True, a lot of WYSIWYG page designers create horrible code, but there’s no reason to assume that Thermo will too.

Actually, I think Flex separates visual design from code so completely that the code isn’t really affected by the visual design. I’m just speculating, but I think it works this way:
1. You create a visual design like you would in Photoshop or Fireworks.
2. You give the elements in the visual design an ID. Those IDs are compiled in an XML document.
3. The code describes what to do with those elements in the XML document.

That means you could move the visual elements anywhere you want and style them any way you want without really affecting the code.

]]> By: jonm http://digitalstevenson.com/jeff/blog/archives/25#comment-40 jonm Wed, 03 Oct 2007 21:02:46 +0000 http://digitalstevenson.com/jeff/blog/archives/25#comment-40 Jeff, I really hope you aren't supporting another wysiwyg. Ugh! I think I may have to start calling you a "mud-coder." Yes, I did just combine a Harry Potter reference with web development. Wow, my nerd plurality is really shining today... Jeff, I really hope you aren’t supporting another wysiwyg. Ugh!

I think I may have to start calling you a “mud-coder.”

Yes, I did just combine a Harry Potter reference with web development. Wow, my nerd plurality is really shining today…

]]>