<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Flash Catalyst gives me the creeps</title>
	<atom:link href="http://blog.sommestad.net/2009/03/flash-catalyst-gives-me-the-creeps-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.sommestad.net/2009/03/flash-catalyst-gives-me-the-creeps-2/</link>
	<description>Web and Cocoa development through the eyes of Kristofer Sommestad, a SWAD developer.</description>
	<lastBuildDate>Tue, 06 Jul 2010 11:48:28 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>By: esset</title>
		<link>http://blog.sommestad.net/2009/03/flash-catalyst-gives-me-the-creeps-2/#comment-63</link>
		<dc:creator>esset</dc:creator>
		<pubDate>Wed, 01 Apr 2009 21:14:12 +0000</pubDate>
		<guid isPermaLink="false">http://reallyaced.wordpress.com/?p=56#comment-63</guid>
		<description>(Moved from the other post :))

Maybe that’s why I wrote the post later? ;)

On a more serious note; yes, if it works as intended it would truly speed up the iterations and give more value. But my ranting was mainly about me not believing it would work, given previous experiences of similar products…

But Adobe’s goal with Catalst is to improve productivity, so if they put enough effort in it, maybe it’ll work? Let’s hope so.

Was at an Adobe seminar today which gave me more insight on FC. Making a new post on the issue…</description>
		<content:encoded><![CDATA[<p>(Moved from the other post <img src='http://blog.sommestad.net/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> )</p>
<p>Maybe that’s why I wrote the post later? <img src='http://blog.sommestad.net/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
<p>On a more serious note; yes, if it works as intended it would truly speed up the iterations and give more value. But my ranting was mainly about me not believing it would work, given previous experiences of similar products…</p>
<p>But Adobe’s goal with Catalst is to improve productivity, so if they put enough effort in it, maybe it’ll work? Let’s hope so.</p>
<p>Was at an Adobe seminar today which gave me more insight on FC. Making a new post on the issue…</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Niklas Gawell</title>
		<link>http://blog.sommestad.net/2009/03/flash-catalyst-gives-me-the-creeps-2/#comment-62</link>
		<dc:creator>Niklas Gawell</dc:creator>
		<pubDate>Wed, 01 Apr 2009 16:33:00 +0000</pubDate>
		<guid isPermaLink="false">http://reallyaced.wordpress.com/?p=56#comment-62</guid>
		<description>... now posting on the correct original post.

To some extent you are contradicting your later posts here. Tools that speeds up the development cycle shortens iteration lenghts, giving the development team more time to rework and hopefully produce more value in the end.

I agree with you that many WYSIWYG tools creates crap, but I think the future is in this direction. Dunno if Catalyst is one of the good or the bad guys though.</description>
		<content:encoded><![CDATA[<p>&#8230; now posting on the correct original post.</p>
<p>To some extent you are contradicting your later posts here. Tools that speeds up the development cycle shortens iteration lenghts, giving the development team more time to rework and hopefully produce more value in the end.</p>
<p>I agree with you that many WYSIWYG tools creates crap, but I think the future is in this direction. Dunno if Catalyst is one of the good or the bad guys though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: esset</title>
		<link>http://blog.sommestad.net/2009/03/flash-catalyst-gives-me-the-creeps-2/#comment-61</link>
		<dc:creator>esset</dc:creator>
		<pubDate>Fri, 27 Mar 2009 11:58:11 +0000</pubDate>
		<guid isPermaLink="false">http://reallyaced.wordpress.com/?p=56#comment-61</guid>
		<description>Hey Ryan,
Thanks for the reply!
My ranting is mainly based on previous use of WYSIWYG editors (in which category I&#039;ve placed FC).
My main concern is that &quot;weird&quot; (from a developer&#039;s point of view) changes will be made in the Catalyst environment, which could cause regression bugs etc.

But maybe I just haven&#039;t gotten a proper view of how Catalyst will work in a real production pipeline (?).

It&#039;ll be interesting to test it for real, but my scepticism will remain until the beta proves me wrong. :)</description>
		<content:encoded><![CDATA[<p>Hey Ryan,<br />
Thanks for the reply!<br />
My ranting is mainly based on previous use of WYSIWYG editors (in which category I&#8217;ve placed FC).<br />
My main concern is that &#8220;weird&#8221; (from a developer&#8217;s point of view) changes will be made in the Catalyst environment, which could cause regression bugs etc.</p>
<p>But maybe I just haven&#8217;t gotten a proper view of how Catalyst will work in a real production pipeline (?).</p>
<p>It&#8217;ll be interesting to test it for real, but my scepticism will remain until the beta proves me wrong. <img src='http://blog.sommestad.net/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Stewart</title>
		<link>http://blog.sommestad.net/2009/03/flash-catalyst-gives-me-the-creeps-2/#comment-60</link>
		<dc:creator>Ryan Stewart</dc:creator>
		<pubDate>Thu, 26 Mar 2009 08:16:00 +0000</pubDate>
		<guid isPermaLink="false">http://reallyaced.wordpress.com/?p=56#comment-60</guid>
		<description>Thanks for the post. Designers won&#039;t be able to ruin your code because you get control of everything. You&#039;ll use a merge tool to bring in whatever the designer changes in Catalyst. I think that most development shops will find their own ways around the workflow. Catalyst makes a great FXG editor and I think it will be pretty easy for developers to bring FXG changes into the components without interfering in what you&#039;re doing.

I&#039;d love to hear from you after we release the public beta on what you think about it.

=Ryan
ryan@adobe.com</description>
		<content:encoded><![CDATA[<p>Thanks for the post. Designers won&#8217;t be able to ruin your code because you get control of everything. You&#8217;ll use a merge tool to bring in whatever the designer changes in Catalyst. I think that most development shops will find their own ways around the workflow. Catalyst makes a great FXG editor and I think it will be pretty easy for developers to bring FXG changes into the components without interfering in what you&#8217;re doing.</p>
<p>I&#8217;d love to hear from you after we release the public beta on what you think about it.</p>
<p>=Ryan<br />
<a href="mailto:ryan@adobe.com">ryan@adobe.com</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

