<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Thermo - It&#8217;s Looking sweet</title>
	<atom:link href="http://blog.flashgen.com/2008/02/27/thermo-its-looking-sweet/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.flashgen.com/2008/02/27/thermo-its-looking-sweet/</link>
	<description>An infrequent look at developments in the world of the Flash Platform</description>
	<pubDate>Sun, 07 Sep 2008 16:29:53 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: FlashGen</title>
		<link>http://blog.flashgen.com/2008/02/27/thermo-its-looking-sweet/#comment-170421</link>
		<dc:creator>FlashGen</dc:creator>
		<pubDate>Sun, 16 Mar 2008 16:19:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.flashgen.com/2008/02/27/thermo-its-looking-sweet/#comment-170421</guid>
		<description>Thanks for the link to the LFPUG presentation on Thermo Tink.</description>
		<content:encoded><![CDATA[<p>Thanks for the link to the LFPUG presentation on Thermo Tink.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: FlashGen</title>
		<link>http://blog.flashgen.com/2008/02/27/thermo-its-looking-sweet/#comment-161508</link>
		<dc:creator>FlashGen</dc:creator>
		<pubDate>Wed, 27 Feb 2008 15:32:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.flashgen.com/2008/02/27/thermo-its-looking-sweet/#comment-161508</guid>
		<description>@creacog The eclipse bit surprised me and I'm not sure if it will end up as an eclipse app. I just happened to spot the "Eclipse" entry in the OS X menu bar as Thermo was closed down, the same way Flex Builder displays it as it goes through the final shut down / clean up routine. 

You're right though it does make sense to have it as both standalone and as the actual design view for FB, we can only wait and see what eventually happens :p

I know where you're coming from with the amount of apps you need to have on your machine these days. Thank God hard disk space is so cheap LOL!</description>
		<content:encoded><![CDATA[<p>@creacog The eclipse bit surprised me and I&#8217;m not sure if it will end up as an eclipse app. I just happened to spot the &#8220;Eclipse&#8221; entry in the OS X menu bar as Thermo was closed down, the same way Flex Builder displays it as it goes through the final shut down / clean up routine. </p>
<p>You&#8217;re right though it does make sense to have it as both standalone and as the actual design view for FB, we can only wait and see what eventually happens :p</p>
<p>I know where you&#8217;re coming from with the amount of apps you need to have on your machine these days. Thank God hard disk space is so cheap LOL!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: creacog</title>
		<link>http://blog.flashgen.com/2008/02/27/thermo-its-looking-sweet/#comment-161489</link>
		<dc:creator>creacog</dc:creator>
		<pubDate>Wed, 27 Feb 2008 15:05:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.flashgen.com/2008/02/27/thermo-its-looking-sweet/#comment-161489</guid>
		<description>I guess my first thoughts on seeing it at LFPUG last week were that it looks like the 'missing design view' of Flex Builder. I didn't realise it was built upon eclipse, so hearing that is great. However it was pretty firmly presented as 'aimed at the designer'. I think they do need to consider that developers are going to be needing it too. Not all designers will wish to spend their time working or tweaking implementation despite the increased ease Thermo presents. As a developer, I find I need to equip myself with most of the tools a designer has, in order to avoid time consuming round-trips when a tweak is required within the creative. Expensive business with a lots spent on some tools only occasionally used! I'm therefore thinking developers who's invested loads into Adobe tools really deserve this properly integrated into builder and designers if they think they need it, should perhaps buy it as a tool ? ;-)  Of course for less than it would cost for them to buy Builder.</description>
		<content:encoded><![CDATA[<p>I guess my first thoughts on seeing it at LFPUG last week were that it looks like the &#8216;missing design view&#8217; of Flex Builder. I didn&#8217;t realise it was built upon eclipse, so hearing that is great. However it was pretty firmly presented as &#8216;aimed at the designer&#8217;. I think they do need to consider that developers are going to be needing it too. Not all designers will wish to spend their time working or tweaking implementation despite the increased ease Thermo presents. As a developer, I find I need to equip myself with most of the tools a designer has, in order to avoid time consuming round-trips when a tweak is required within the creative. Expensive business with a lots spent on some tools only occasionally used! I&#8217;m therefore thinking developers who&#8217;s invested loads into Adobe tools really deserve this properly integrated into builder and designers if they think they need it, should perhaps buy it as a tool ? ;-)  Of course for less than it would cost for them to buy Builder.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
