Revision: 2845 http://trac.macosforge.org/projects/ruby/changeset/2845 Author: joshua.ballanco@apple.com Date: 2009-10-17 19:55:02 -0700 (Sat, 17 Oct 2009) Log Message: ----------- Fixing a few typos Modified Paths: -------------- MacRubyWebsite/trunk/content/recipes/tdd-in-objective-c-with-macruby.txt Modified: MacRubyWebsite/trunk/content/recipes/tdd-in-objective-c-with-macruby.txt =================================================================== --- MacRubyWebsite/trunk/content/recipes/tdd-in-objective-c-with-macruby.txt 2009-10-18 00:49:53 UTC (rev 2844) +++ MacRubyWebsite/trunk/content/recipes/tdd-in-objective-c-with-macruby.txt 2009-10-18 02:55:02 UTC (rev 2845) @@ -86,7 +86,7 @@ h2. The First Iteration -Now that we have everything set-up, it's time to get to work. Since this is the first time doing TDD of Objective-C with Ruby, we'll take it slow. Our first spec will simply test instantiation of a translator object. Go back to the Xcode editor, and add the following to your pltranslator_spec.rb file: +Now that we have everything set-up, it's time to get to work. Since this is our first time doing TDD of Objective-C with MacRuby, we'll take it slow. Our first spec will simply test instantiation of a translator object. Go back to the Xcode editor, and add the following to your pltranslator_spec.rb file: <% coderay :lang => 'ruby' do -%> # pltranslator_spec.rb @@ -274,9 +274,9 @@ h2. Going further... -Hopefully, by now you're starting to see just how useful testing Objective-C with MacRuby can be. As an exercise to improve your skills, try implementing the reverse translation. You can start by reversing the keys and values we used in the tests above. What other corner cases can you think of? Can your write some specs to flush out the behavior of our framework class? +Hopefully, by now you're starting to see just how useful testing Objective-C with MacRuby can be. As an exercise to improve your skills, try implementing the reverse translation. You can start by reversing the keys and values we used in the test above. What other corner cases can you think of? Can you write some specs to flush out the behavior of our framework class? -Be creative! Now that you can access Objective-C objects from MacRuby, it's not only possible to use Cocoa to improve your Ruby, but it's also possible to use Ruby to improve your Objective-C. For example, once you've got a pretty good set of specs covering the PLTranslator.rb class, throw it away and rewrite it in Ruby! Try this for another Cocoa class, or even take a Ruby library with extensive test coverage, and use those tests as a scaffold to rewrite the library in Objective-C. +Be creative! Now that you can access Objective-C objects from MacRuby, it's not only possible to use Cocoa to improve your Ruby, but it's also possible to use Ruby to improve your Objective-C. For example, once you've got a pretty good set of specs covering the PLTranslator class, throw it away and rewrite it in Ruby! Try this for another Cocoa class, or even take a Ruby library with extensive test coverage, and use those tests as a scaffold to rewrite the library in Objective-C. Also, don't forget that, while Ruby requires that a framework be compatible with the Objective-C garbage collector, the framework does not have to be strictly garbage collected. So, you could even use Bacon to spec out an Objective-C framework running with the GC turned on, then add in "retain"s and "release"s and use that same framework on the iPhone.