<?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: Should Adobe buy Aptana?</title>
	<atom:link href="http://blog.flashgen.com/2007/10/31/should-adobe-buy-aptana/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.flashgen.com/2007/10/31/should-adobe-buy-aptana/</link>
	<description>An infrequent look at developments in the world of the Flash Platform</description>
	<pubDate>Mon, 13 Oct 2008 07:03:20 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: FlashGen</title>
		<link>http://blog.flashgen.com/2007/10/31/should-adobe-buy-aptana/#comment-145982</link>
		<dc:creator>FlashGen</dc:creator>
		<pubDate>Wed, 30 Jan 2008 07:06:58 +0000</pubDate>
		<guid isPermaLink="false">http://blog.flashgen.com/2007/10/31/should-adobe-buy-aptana/#comment-145982</guid>
		<description>@Ramin, thanks for the tip. I had noticed this issue - loads of little red circles with a crosses in them. I tend to just close the Aptana perspective and that seems to do the same. However, as you point out if you have FB3 and Aptana active together then your only recourse is to disable Aptana's CSS validation.

BTW if you use OxygenXML as well then it gets really awkward - OxygenXML tries to steal .css file association so you tend to have to reset the default .css associated editor view from time to time.

Again, thanks for the tip I'm sure others are suffering with this too :p</description>
		<content:encoded><![CDATA[<p>@Ramin, thanks for the tip. I had noticed this issue - loads of little red circles with a crosses in them. I tend to just close the Aptana perspective and that seems to do the same. However, as you point out if you have FB3 and Aptana active together then your only recourse is to disable Aptana&#8217;s CSS validation.</p>
<p>BTW if you use OxygenXML as well then it gets really awkward - OxygenXML tries to steal .css file association so you tend to have to reset the default .css associated editor view from time to time.</p>
<p>Again, thanks for the tip I&#8217;m sure others are suffering with this too :p</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ramin</title>
		<link>http://blog.flashgen.com/2007/10/31/should-adobe-buy-aptana/#comment-145755</link>
		<dc:creator>ramin</dc:creator>
		<pubDate>Tue, 29 Jan 2008 21:44:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.flashgen.com/2007/10/31/should-adobe-buy-aptana/#comment-145755</guid>
		<description>The latest update to Aptana causes compilation problems in FB3 beta 3 with stylesheets. The problem seems to be with the W3 validator not understanding the Flex CSS extensions. The only solution seems to be to disable Aptana's CSS validation. Go to Eclipse Preferences -&#62; Aptana/Editors/CSS/Validation and turn off the checkbox next to "W3C Stylesheet Validator' and apply.

You can also change the default editor for CSS in Preferences-&#62;General/Editors/File Associations for *.css away from Aptana to anything else (and hitting the 'Default' button).

HTH.</description>
		<content:encoded><![CDATA[<p>The latest update to Aptana causes compilation problems in FB3 beta 3 with stylesheets. The problem seems to be with the W3 validator not understanding the Flex CSS extensions. The only solution seems to be to disable Aptana&#8217;s CSS validation. Go to Eclipse Preferences -&gt; Aptana/Editors/CSS/Validation and turn off the checkbox next to &#8220;W3C Stylesheet Validator&#8217; and apply.</p>
<p>You can also change the default editor for CSS in Preferences-&gt;General/Editors/File Associations for *.css away from Aptana to anything else (and hitting the &#8216;Default&#8217; button).</p>
<p>HTH.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: marc</title>
		<link>http://blog.flashgen.com/2007/10/31/should-adobe-buy-aptana/#comment-107849</link>
		<dc:creator>marc</dc:creator>
		<pubDate>Wed, 31 Oct 2007 18:32:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.flashgen.com/2007/10/31/should-adobe-buy-aptana/#comment-107849</guid>
		<description>Thanks for this great and detailed entry. Indeed I never heard about this editor. Am currently downloading the pro-test version. Thanks again and see you on sunday, I guess...</description>
		<content:encoded><![CDATA[<p>Thanks for this great and detailed entry. Indeed I never heard about this editor. Am currently downloading the pro-test version. Thanks again and see you on sunday, I guess&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: FlashGen</title>
		<link>http://blog.flashgen.com/2007/10/31/should-adobe-buy-aptana/#comment-107833</link>
		<dc:creator>FlashGen</dc:creator>
		<pubDate>Wed, 31 Oct 2007 17:03:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.flashgen.com/2007/10/31/should-adobe-buy-aptana/#comment-107833</guid>
		<description>@Ethan, I know what you mean by DW getting a bit porky. However it does offer a lot for it's memory footprint. I'm not sure I'd want Adobe to hypothetically shoe horn the design view from DW into an eclipse based app. A more focused approach would be to build on  / improve the Flex Builder design view - perhaps this is where Thermo could step up to the plate...

@Jim, I agree with your concerns about a community version. I think anyone who bought a company that had an open source project would have real problems trying to close source it.
On a side note, as it happens the latest version of Flex Builder 3 (beta 2) has CFEclipse as part of the update site list. So we are getting one step closer at least.</description>
		<content:encoded><![CDATA[<p>@Ethan, I know what you mean by DW getting a bit porky. However it does offer a lot for it&#8217;s memory footprint. I&#8217;m not sure I&#8217;d want Adobe to hypothetically shoe horn the design view from DW into an eclipse based app. A more focused approach would be to build on  / improve the Flex Builder design view - perhaps this is where Thermo could step up to the plate&#8230;</p>
<p>@Jim, I agree with your concerns about a community version. I think anyone who bought a company that had an open source project would have real problems trying to close source it.<br />
On a side note, as it happens the latest version of Flex Builder 3 (beta 2) has CFEclipse as part of the update site list. So we are getting one step closer at least.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim</title>
		<link>http://blog.flashgen.com/2007/10/31/should-adobe-buy-aptana/#comment-107824</link>
		<dc:creator>Jim</dc:creator>
		<pubDate>Wed, 31 Oct 2007 16:28:42 +0000</pubDate>
		<guid isPermaLink="false">http://blog.flashgen.com/2007/10/31/should-adobe-buy-aptana/#comment-107824</guid>
		<description>I've blogged about the possibilities of CFEclipse merging with Aptana.   I think Mark Drew and the Aptana people have spoken - but not sure what the status is on that.

http://www.thecrumb.com/2007/09/21/should-cfeclipse-and-aptana-merge/

As long as they can keep a full featured, free, community edition available I wouldn't have any issues with Adobe buying them :)</description>
		<content:encoded><![CDATA[<p>I&#8217;ve blogged about the possibilities of CFEclipse merging with Aptana.   I think Mark Drew and the Aptana people have spoken - but not sure what the status is on that.</p>
<p><a href="http://www.thecrumb.com/2007/09/21/should-cfeclipse-and-aptana-merge/" rel="nofollow">http://www.thecrumb.com/2007/09/21/should-cfeclipse-and-aptana-merge/</a></p>
<p>As long as they can keep a full featured, free, community edition available I wouldn&#8217;t have any issues with Adobe buying them :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ethan Estes</title>
		<link>http://blog.flashgen.com/2007/10/31/should-adobe-buy-aptana/#comment-107809</link>
		<dc:creator>Ethan Estes</dc:creator>
		<pubDate>Wed, 31 Oct 2007 14:45:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.flashgen.com/2007/10/31/should-adobe-buy-aptana/#comment-107809</guid>
		<description>I agree, but i see that they could take the designer side of DW (which is similiar to FB) and add it to aptana. Then they could diable the wizards for the more developer type in prefs. DW just seems so heavy these days-i think it needs a clean out.</description>
		<content:encoded><![CDATA[<p>I agree, but i see that they could take the designer side of DW (which is similiar to FB) and add it to aptana. Then they could diable the wizards for the more developer type in prefs. DW just seems so heavy these days-i think it needs a clean out.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
