<?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: Switch from PureMvc to Mate for Flex development (ToDoList 2010)</title>
	<atom:link href="http://blog.rive.be/2009/11/19/switch-from-puremvc-to-mate-for-flex-development-todolist-2010/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.rive.be/2009/11/19/switch-from-puremvc-to-mate-for-flex-development-todolist-2010/</link>
	<description>Flash Platform Development. Mobile, Web &#38; Desktop Applications.</description>
	<lastBuildDate>Fri, 12 Feb 2010 14:50:01 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Rien Verbrugghe</title>
		<link>http://blog.rive.be/2009/11/19/switch-from-puremvc-to-mate-for-flex-development-todolist-2010/comment-page-1/#comment-129</link>
		<dc:creator>Rien Verbrugghe</dc:creator>
		<pubDate>Fri, 20 Nov 2009 09:38:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.rive.be/?p=470#comment-129</guid>
		<description>Nice! I just saw the video at http://www.firemoss.com/index.cfm/2009/10/21/Swiz-in-20-minutes-video--byebye-boilerplate and I must say. Swiz looks great too. Only, I wish there was as much documentation available as for Mate. Just google and you&#039;ll see the difference. That makes me holding back to start using it in a project. Check out this http://tv.adobe.com/watch/360flex-conference/introduction-to-the-swiz-framework-for-flex-by-chris-scott and this too Mate vs Swiz http://www.darronschall.com/presentations/2009/10/08/Mate%20vs%20Swiz.pdf</description>
		<content:encoded><![CDATA[<p>Nice! I just saw the video at <a href="http://www.firemoss.com/index.cfm/2009/10/21/Swiz-in-20-minutes-video--byebye-boilerplate" rel="nofollow">http://www.firemoss.com/index.cfm/2009/10/21/Swiz-in-20-minutes-video&#8211;byebye-boilerplate</a> and I must say. Swiz looks great too. Only, I wish there was as much documentation available as for Mate. Just google and you&#8217;ll see the difference. That makes me holding back to start using it in a project. Check out this <a href="http://tv.adobe.com/watch/360flex-conference/introduction-to-the-swiz-framework-for-flex-by-chris-scott" rel="nofollow">http://tv.adobe.com/watch/360flex-conference/introduction-to-the-swiz-framework-for-flex-by-chris-scott</a> and this too Mate vs Swiz <a href="http://www.darronschall.com/presentations/2009/10/08/Mate%20vs%20Swiz.pdf" rel="nofollow">http://www.darronschall.com/presentations/2009/10/08/Mate%20vs%20Swiz.pdf</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lordy</title>
		<link>http://blog.rive.be/2009/11/19/switch-from-puremvc-to-mate-for-flex-development-todolist-2010/comment-page-1/#comment-126</link>
		<dc:creator>Lordy</dc:creator>
		<pubDate>Thu, 19 Nov 2009 20:34:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.rive.be/?p=470#comment-126</guid>
		<description>Mate probably won&#039;t reduce the number of classes you already have, a properly architected app will still require good separation, but it will give you a more flexibility when you just want to try certain things out and want to mock stuff in place of better written code. Plus it is sooooo nice not having to extend, or mix in framework classes just to fit convention, you can always convince yourself that you can switch to entire different framework in the future ( not that you ever would! )</description>
		<content:encoded><![CDATA[<p>Mate probably won&#8217;t reduce the number of classes you already have, a properly architected app will still require good separation, but it will give you a more flexibility when you just want to try certain things out and want to mock stuff in place of better written code. Plus it is sooooo nice not having to extend, or mix in framework classes just to fit convention, you can always convince yourself that you can switch to entire different framework in the future ( not that you ever would! )</p>
]]></content:encoded>
	</item>
</channel>
</rss>
