<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/stylesheets/rss.css" type="text/css"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>HCoder.org: Tag problems</title>
    <link>http://www.hcoder.org/articles/tag/problems</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description></description>
    <item>
      <title>Haberdasher and Rails 2.0</title>
      <description>&lt;p&gt;I&amp;#8217;m kind of back to Haberdasher work, so I&amp;#8217;m playing again with Rails. However, I&amp;#8217;m a very late adopter for many things, and that included Rails because I wasn&amp;#8217;t that interested in investing time in learning all the new stuff and porting my applications to the new version.&lt;/p&gt;


	&lt;p&gt;But the universe had its own ideas about Rails 2.0 and me, so I had some retarded compatibility problems with Haberdasher and the up-to-date &lt;code&gt;rake&lt;/code&gt; utility version in Debian. The problems were related to some Rails plugins I was using, and they made me have a look at upgrading to Rails 2.0 from Rails 1.2. It turned out to be really easy to do, the hardest &lt;em&gt;by far&lt;/em&gt; was replacing the plugins that gave problems with application code or other plugins (yes, I know that if I was going to get rid of them anyway, I might as well have stayed in Rails 1.2, I just thought it was a good idea to upgrade if I was going to resume Haberdasher development).&lt;/p&gt;


	&lt;p&gt;To be honest I haven&amp;#8217;t really learned new stuff yet. I&amp;#8217;m just using the same things I was using, only now powered by Rails 2.0. A couple of improvements/clean ups in syntax, deprecated code removal and similar, but nothing big yet.&lt;/p&gt;


	&lt;p&gt;The other news is that now that I have a working Haberdasher again, I&amp;#8217;m making some changes I had in mind since months ago, namely adding some user preferences &amp;#8220;framework&amp;#8221;, and adding the ability to assign a copyright notice to the patches (with a configurable default notice per user, hence the user preferences). I haven&amp;#8217;t published this work yet, but I plan to do it in a couple of days, after updating the demo installation and checking that everything&amp;#8217;s alright.&lt;/p&gt;</description>
      <pubDate>Sun, 02 Mar 2008 22:57:00 +0000</pubDate>
      <guid isPermaLink="false">urn:uuid:b0bb2623-0335-4536-99ea-d1cbba85c08b</guid>
      <author>Esteban Manchado</author>
      <link>http://www.hcoder.org/articles/2008/03/02/haberdasher-and-rails-2-0</link>
      <category>Haberdasher</category>
      <category>Ruby</category>
      <category>rails</category>
      <category>upgrading</category>
      <category>compatibility</category>
      <category>problems</category>
      <category>plugins</category>
      <category>rake</category>
    </item>
  </channel>
</rss>
