<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/css" href="/stylesheets/rss.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>The Bacon Bear Blog: So far so good!</title>
    <link>http://www.baconbear.com/articles/2007/09/19/so-far-so-good</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description></description>
    <item>
      <title>So far so good!</title>
      <description>&lt;p&gt;Couple days into playing with RubyCocoa and its so far so good!  The toughest part of learning any new framework is learning the framework&amp;#8217;s terminology and Cocoa&amp;#8217;s no exception.  Nibs, outlets, selectors, bindings&amp;#8230;  All foreign concepts if you&amp;#8217;ve never worked in Cocoa before.  Luckily the online tutorials are fairly good and Apple&amp;#8217;s documentation is excellent.&lt;/p&gt;

&lt;p&gt;The only problem i&amp;#8217;ve run into so far turned out to be my own damned fault.  I&amp;#8217;m doing a lot of the RESTful heavy lifting using &lt;a href="http://svn.rubyonrails.org/rails/trunk/activeresource/"&gt;ActiveResource&lt;/a&gt; and it really doesn&amp;#8217;t like receiving NSStrings as parameters.  So much so that it crashes the App.  No good.  No good at all.  &lt;/p&gt;

&lt;p&gt;Remember kids, NSString != ruby string.  to_s is your friend.&lt;/p&gt;</description>
      <pubDate>Wed, 19 Sep 2007 19:03:00 -0700</pubDate>
      <guid isPermaLink="false">urn:uuid:dcc0f1f4-e874-4e05-9c1e-cedb770dbefc</guid>
      <author>Jeff</author>
      <link>http://www.baconbear.com/articles/2007/09/19/so-far-so-good</link>
      <category>rails</category>
    </item>
  </channel>
</rss>
