<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Sat, 18 May 2013 19:39:32 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[LoLoCoJr Blog:  Rewriting a (large) PHP application in Rails, part 2]]></title>
      <guid>http://www.phpdeveloper.org/news/6948</guid>
      <link>http://www.phpdeveloper.org/news/6948</link>
      <description><![CDATA[<p>
The LoLoCoJr site has published <a href="http://www.railsguru.com/articles/2006/12/19/rewriting-a-large-php-application-in-rails-part-2">part two</a> of the series (<a href="http://www.phpdeveloper.org/news/6895">part one</a> is here) about converting a PHP application over to Rails.
</p>
<blockquote>
In my <a href="http://www.railsguru.com/articles/2006/12/13/convertinga-large-php-application-to-rails-part-1">previous post</a> on this topic I described the method we used to convert a legacy MySQL PHP database to a Rails conformant PostgreSQL hosted version. In this article I will tell a bit about how we converted the HTML of the application to Rails layout templates and partials.
</blockquote>
<p>
It's a <a href="http://www.railsguru.com/articles/2006/12/19/rewriting-a-large-php-application-in-rails-part-2">quickpost</a> this time showing how to extract the rendered HTML from the page's output, writing out some of the business logic, and a mention of test driven development versus write test after developing methods.
</p>]]></description>
      <pubDate>Wed, 20 Dec 2006 10:17:00 -0600</pubDate>
    </item>
  </channel>
</rss>
