<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments for Chris Cruft</title>
	<link>http://cho.hapgoods.com/wordpress</link>
	<description>A Fount of Worthless Drivel</description>
	<pubDate>Wed, 08 Sep 2010 19:36:05 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.3</generator>

	<item>
		<title>Comment on Ruby, Rails and MySQL with Leopard 10.5.2 and XCode 3.0 by CantRemembrances &#187; Blog Archive &#187; Upgrading your Rails Development Mac to Snow Leopard</title>
		<link>http://cho.hapgoods.com/wordpress/?p=158#comment-2069</link>
		<dc:creator>CantRemembrances &#187; Blog Archive &#187; Upgrading your Rails Development Mac to Snow Leopard</dc:creator>
		<pubDate>Sun, 07 Feb 2010 06:17:23 +0000</pubDate>
		<guid>http://cho.hapgoods.com/wordpress/?p=158#comment-2069</guid>
		<description>[...] 1.8.7 on my personal machine. Either path is fine, just pick up the latest source of your choosing. Chris Cruft&#8217;s blog post goes into some of the details I&#8217;m describing here as well. Basically, the README boils down [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] 1.8.7 on my personal machine. Either path is fine, just pick up the latest source of your choosing. Chris Cruft&#8217;s blog post goes into some of the details I&#8217;m describing here as well. Basically, the README boils down [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Ruby, Rails and MySQL with Leopard 10.5.2 and XCode 3.0 by cch1</title>
		<link>http://cho.hapgoods.com/wordpress/?p=158#comment-1932</link>
		<dc:creator>cch1</dc:creator>
		<pubDate>Mon, 19 Oct 2009 01:27:27 +0000</pubDate>
		<guid>http://cho.hapgoods.com/wordpress/?p=158#comment-1932</guid>
		<description>And two years after taking the easy way out, Snow Leopard finally adds 64-bit libraries and Ruby stuff to make the x86_64 architecture viable.  Witness:

	bimota:~ root# file /usr/bin/ruby
	/usr/bin/ruby: Mach-O universal binary with 3 architectures
	/usr/bin/ruby (for architecture x86_64):        Mach-O 64-bit executable x86_64
	/usr/bin/ruby (for architecture i386):  Mach-O executable i386
	/usr/bin/ruby (for architecture ppc7400):       Mach-O executable ppc

So now we can install the x86_64 binary from MySQL and move on.</description>
		<content:encoded><![CDATA[<p>And two years after taking the easy way out, Snow Leopard finally adds 64-bit libraries and Ruby stuff to make the x86_64 architecture viable.  Witness:</p>
<p>	bimota:~ root# file /usr/bin/ruby<br />
	/usr/bin/ruby: Mach-O universal binary with 3 architectures<br />
	/usr/bin/ruby (for architecture x86_64):        Mach-O 64-bit executable x86_64<br />
	/usr/bin/ruby (for architecture i386):  Mach-O executable i386<br />
	/usr/bin/ruby (for architecture ppc7400):       Mach-O executable ppc</p>
<p>So now we can install the x86_64 binary from MySQL and move on.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A multitude of method_missing monstrosities by cch1</title>
		<link>http://cho.hapgoods.com/wordpress/?p=128#comment-1903</link>
		<dc:creator>cch1</dc:creator>
		<pubDate>Tue, 25 Aug 2009 15:25:25 +0000</pubDate>
		<guid>http://cho.hapgoods.com/wordpress/?p=128#comment-1903</guid>
		<description>Since the time I wrote the above post, Rails has really moved a long way towards addressing my needs without bringing the model scoping directly into the controller.  Clearly the coupling of model scope and controller is not something the Rails core team wants, but I applaud the excellent functionality now available in scoping (named_scopes, default scopes).  Named scope composition alone is a HUGE jump in expressiveness and neatly addresses my orthogonality concerns noted above (with the minor nit that Base.find doesn't return a scope-compatible object -see below).

I'd like to see a grand unified theory of object retrieval that unifies AR::Base.find, associations and named scopes into a single concept.  We're definitely getting closer.

Somewhat related cool idea: Rails provides three default scopes (AFAICT): first, last and all.  Why not add "inverse"?  For example, Widgets.red.new.inverse would result in something like this...

SELECT * FROM widgets WHERE id NOT IN (SELECT id FROM widgets WHERE color = 'red' AND condition = 'new')</description>
		<content:encoded><![CDATA[<p>Since the time I wrote the above post, Rails has really moved a long way towards addressing my needs without bringing the model scoping directly into the controller.  Clearly the coupling of model scope and controller is not something the Rails core team wants, but I applaud the excellent functionality now available in scoping (named_scopes, default scopes).  Named scope composition alone is a HUGE jump in expressiveness and neatly addresses my orthogonality concerns noted above (with the minor nit that Base.find doesn&#8217;t return a scope-compatible object -see below).</p>
<p>I&#8217;d like to see a grand unified theory of object retrieval that unifies AR::Base.find, associations and named scopes into a single concept.  We&#8217;re definitely getting closer.</p>
<p>Somewhat related cool idea: Rails provides three default scopes (AFAICT): first, last and all.  Why not add &#8220;inverse&#8221;?  For example, Widgets.red.new.inverse would result in something like this&#8230;</p>
<p>SELECT * FROM widgets WHERE id NOT IN (SELECT id FROM widgets WHERE color = &#8216;red&#8217; AND condition = &#8216;new&#8217;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on YAML Fixtures for Serialized Objects by cch1</title>
		<link>http://cho.hapgoods.com/wordpress/?p=126#comment-1902</link>
		<dc:creator>cch1</dc:creator>
		<pubDate>Tue, 25 Aug 2009 14:54:39 +0000</pubDate>
		<guid>http://cho.hapgoods.com/wordpress/?p=126#comment-1902</guid>
		<description>I've updated this post to ensure that control characters are properly rendered in the ERB snippets embedded within the YAML.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve updated this post to ensure that control characters are properly rendered in the ERB snippets embedded within the YAML.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on YAML Fixtures for Serialized Objects by Chris Cruft Blog Archive YAML Fixtures for Serialized Objects &#124; Outdoor Ceiling Fans</title>
		<link>http://cho.hapgoods.com/wordpress/?p=126#comment-1808</link>
		<dc:creator>Chris Cruft Blog Archive YAML Fixtures for Serialized Objects &#124; Outdoor Ceiling Fans</dc:creator>
		<pubDate>Sun, 31 May 2009 12:43:13 +0000</pubDate>
		<guid>http://cho.hapgoods.com/wordpress/?p=126#comment-1808</guid>
		<description>[...] Chris Cruft Blog Archive YAML Fixtures for Serialized Objects   Posted by root 6 hours ago (http://cho.hapgoods.com)        Dec 1 2006 there is no direct transfer of the yaml encoded fixture to the database field rails instantiates the object first leave a reply you must be logged in to post a comment chris cruft is proudly powered by wordpress        Discuss&#160;  &#124;&#160; Bury &#124;&#160;    News &#124; Chris Cruft Blog Archive YAML Fixtures for Serialized Objects [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Chris Cruft Blog Archive YAML Fixtures for Serialized Objects   Posted by root 6 hours ago (http://cho.hapgoods.com)        Dec 1 2006 there is no direct transfer of the yaml encoded fixture to the database field rails instantiates the object first leave a reply you must be logged in to post a comment chris cruft is proudly powered by wordpress        Discuss&nbsp;  |&nbsp; Bury |&nbsp;    News | Chris Cruft Blog Archive YAML Fixtures for Serialized Objects [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on YAML Fixtures for Serialized Objects by thenobot</title>
		<link>http://cho.hapgoods.com/wordpress/?p=126#comment-1781</link>
		<dc:creator>thenobot</dc:creator>
		<pubDate>Thu, 16 Apr 2009 18:13:32 +0000</pubDate>
		<guid>http://cho.hapgoods.com/wordpress/?p=126#comment-1781</guid>
		<description>The above solutions did not work for me, however this does:
 data:  'bar', 'baz' =&#62; 'bad' ).to_yaml.sub(/^--- /,"").gsub(/\n/,"\n    ") %&#62;</description>
		<content:encoded><![CDATA[<p>The above solutions did not work for me, however this does:<br />
 data:  &#8216;bar&#8217;, &#8216;baz&#8217; =&gt; &#8216;bad&#8217; ).to_yaml.sub(/^&#8212; /,&#8221;").gsub(/\n/,&#8221;\n    &#8220;) %&gt;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on YAML Fixtures for Serialized Objects by vrtra theory&#187; Blog Archive &#187; Storing serialized arrays in fixtures</title>
		<link>http://cho.hapgoods.com/wordpress/?p=126#comment-1750</link>
		<dc:creator>vrtra theory&#187; Blog Archive &#187; Storing serialized arrays in fixtures</dc:creator>
		<pubDate>Wed, 18 Mar 2009 22:38:52 +0000</pubDate>
		<guid>http://cho.hapgoods.com/wordpress/?p=126#comment-1750</guid>
		<description>[...] found my first solution (and a nice write-up of the problem) at Chris Cruft&#8217;s blog.  He added a gsub that adds extra spaces after each newline in the generated YAML.  Oddly enough, [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] found my first solution (and a nice write-up of the problem) at Chris Cruft&#8217;s blog.  He added a gsub that adds extra spaces after each newline in the generated YAML.  Oddly enough, [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Eclipse Git plugin installation by saltzmanjoelh</title>
		<link>http://cho.hapgoods.com/wordpress/?p=159#comment-1746</link>
		<dc:creator>saltzmanjoelh</dc:creator>
		<pubDate>Fri, 06 Mar 2009 17:49:15 +0000</pubDate>
		<guid>http://cho.hapgoods.com/wordpress/?p=159#comment-1746</guid>
		<description>Turns out it was a limited version of eclipse pdt. I just downloaded Eclipse classic and it gave me my options</description>
		<content:encoded><![CDATA[<p>Turns out it was a limited version of eclipse pdt. I just downloaded Eclipse classic and it gave me my options</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Eclipse Git plugin installation by saltzmanjoelh</title>
		<link>http://cho.hapgoods.com/wordpress/?p=159#comment-1727</link>
		<dc:creator>saltzmanjoelh</dc:creator>
		<pubDate>Fri, 27 Feb 2009 17:12:16 +0000</pubDate>
		<guid>http://cho.hapgoods.com/wordpress/?p=159#comment-1727</guid>
		<description>I followed these steps with my Eclipse App and it worked fine. But, when I try to do it in Flex Builder 3, it doesnt give me the Export Plugin option. I tried the pref, general, capabilities. But, that wasnt there either. I also tried, building and exporting from Eclipse to my Flex Builder Directory and stil nothing. Any suggestions?</description>
		<content:encoded><![CDATA[<p>I followed these steps with my Eclipse App and it worked fine. But, when I try to do it in Flex Builder 3, it doesnt give me the Export Plugin option. I tried the pref, general, capabilities. But, that wasnt there either. I also tried, building and exporting from Eclipse to my Flex Builder Directory and stil nothing. Any suggestions?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Eclipse Git plugin installation by Recent Links Tagged With "eclipse" - JabberTags</title>
		<link>http://cho.hapgoods.com/wordpress/?p=159#comment-1617</link>
		<dc:creator>Recent Links Tagged With "eclipse" - JabberTags</dc:creator>
		<pubDate>Wed, 31 Dec 2008 06:19:41 +0000</pubDate>
		<guid>http://cho.hapgoods.com/wordpress/?p=159#comment-1617</guid>
		<description>[...] 21-12-2008   NetBeans IDE 6.5 Beta for PHP Developers Saved by favoriteangel on Thu 18-12-2008   Chris Cruft » Blog Archive » Eclipse Git plugin installation Saved by flarestart on Tue 16-12-2008   partial eclipse Saved by wikilious on Tue 16-12-2008   [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] 21-12-2008   NetBeans IDE 6.5 Beta for PHP Developers Saved by favoriteangel on Thu 18-12-2008   Chris Cruft » Blog Archive » Eclipse Git plugin installation Saved by flarestart on Tue 16-12-2008   partial eclipse Saved by wikilious on Tue 16-12-2008   [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
