<?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: Preparing for Rails 2.0</title>
	<atom:link href="http://www.sitepoint.com/blogs/2007/10/31/preparing-for-rails-20/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sitepoint.com/blogs/2007/10/31/preparing-for-rails-20/</link>
	<description></description>
	<pubDate>Sat, 30 Aug 2008 11:26:33 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: AkitaOnRails</title>
		<link>http://www.sitepoint.com/blogs/2007/10/31/preparing-for-rails-20/#comment-548096</link>
		<dc:creator>AkitaOnRails</dc:creator>
		<pubDate>Mon, 10 Dec 2007 20:48:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2007/10/31/preparing-for-rails-20/#comment-548096</guid>
		<description>I invite everybody to take a look at a screencast I've compiled yesterday. This is the classic Blog app built using Rails 2.0. I think it is the First Rails 2.0 full featured screencast around.

See it "here":http://www.akitaonrails.com/2007/12/10/the-first-rails-2-0-screencast-english</description>
		<content:encoded><![CDATA[<p>I invite everybody to take a look at a screencast I&#8217;ve compiled yesterday. This is the classic Blog app built using Rails 2.0. I think it is the First Rails 2.0 full featured screencast around.</p>
<p>See it &#8220;here&#8221;:http://www.akitaonrails.com/2007/12/10/the-first-rails-2-0-screencast-english</p>]]></content:encoded>
	</item>
	<item>
		<title>By: MarcelloDL</title>
		<link>http://www.sitepoint.com/blogs/2007/10/31/preparing-for-rails-20/#comment-545476</link>
		<dc:creator>MarcelloDL</dc:creator>
		<pubDate>Sun, 09 Dec 2007 16:56:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2007/10/31/preparing-for-rails-20/#comment-545476</guid>
		<description>render :partial seems not assuming the calling controller anymore, so:

 render :partial =&#62; '/partial'
 
won't work.

 render :partial =&#62; 'controller_name/partial'

will instead pick the partial named "_partial" in app/views/controller_name</description>
		<content:encoded><![CDATA[<p>render :partial seems not assuming the calling controller anymore, so:</p>
<p> render :partial =&gt; &#8216;/partial&#8217;</p>
<p>won&#8217;t work.</p>
<p> render :partial =&gt; &#8216;controller_name/partial&#8217;</p>
<p>will instead pick the partial named &#8220;_partial&#8221; in app/views/controller_name</p>]]></content:encoded>
	</item>
	<item>
		<title>By: yougottabekidding</title>
		<link>http://www.sitepoint.com/blogs/2007/10/31/preparing-for-rails-20/#comment-439463</link>
		<dc:creator>yougottabekidding</dc:creator>
		<pubDate>Tue, 06 Nov 2007 08:21:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2007/10/31/preparing-for-rails-20/#comment-439463</guid>
		<description>A &lt;em&gt;slow&lt;/em&gt; start!? Rails is going like gangbusters, and has for a couple of years. 

ParkinT has it completely backwards.  It is not Rails that has benefited from SitePoint, but SitePoint that has benefited from Rails, capitalizing on its popularity by publishing books.   Rails would be just fine (thank you) without SitePoint.   Not to say the Sitepoint books aren't good, but they cannot in a million years take credit for Rails' success.</description>
		<content:encoded><![CDATA[<p>A <em>slow</em> start!? Rails is going like gangbusters, and has for a couple of years. </p>
<p>ParkinT has it completely backwards.  It is not Rails that has benefited from SitePoint, but SitePoint that has benefited from Rails, capitalizing on its popularity by publishing books.   Rails would be just fine (thank you) without SitePoint.   Not to say the Sitepoint books aren&#8217;t good, but they cannot in a million years take credit for Rails&#8217; success.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: ParkinT</title>
		<link>http://www.sitepoint.com/blogs/2007/10/31/preparing-for-rails-20/#comment-431349</link>
		<dc:creator>ParkinT</dc:creator>
		<pubDate>Wed, 31 Oct 2007 15:21:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2007/10/31/preparing-for-rails-20/#comment-431349</guid>
		<description>Wow. After a slow start, Rails seems to be 'gathering steam'!
I think this is, in large part, due to the recent publications Sitepoint has provided; permitting more developers to get their hands dirty with Ruby on Rails.
I am having fun learning a new language (adding to my current collection of over a dozen) and applying the many lessons offered here.</description>
		<content:encoded><![CDATA[<p>Wow. After a slow start, Rails seems to be &#8216;gathering steam&#8217;!<br />
I think this is, in large part, due to the recent publications Sitepoint has provided; permitting more developers to get their hands dirty with Ruby on Rails.<br />
I am having fun learning a new language (adding to my current collection of over a dozen) and applying the many lessons offered here.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: kommen</title>
		<link>http://www.sitepoint.com/blogs/2007/10/31/preparing-for-rails-20/#comment-431208</link>
		<dc:creator>kommen</dc:creator>
		<pubDate>Wed, 31 Oct 2007 07:15:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2007/10/31/preparing-for-rails-20/#comment-431208</guid>
		<description>There is a little script which checks existing rails for a rough rails 2.0 compatibility:
http://pastie.caboo.se/private/krcevozww61drdeza13e3a</description>
		<content:encoded><![CDATA[<p>There is a little script which checks existing rails for a rough rails 2.0 compatibility:<br />
<a href="http://pastie.caboo.se/private/krcevozww61drdeza13e3a" rel="nofollow">http://pastie.caboo.se/private/krcevozww61drdeza13e3a</a></p>]]></content:encoded>
	</item>
</channel>
</rss>
