<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Disqus - Friends of jamesconroyfinn</title><link>http://disqus.com/by/jamesconroyfinn/</link><description></description><atom:link href="http://disqus.com/jamesconroyfinn/friends.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Mon, 17 Aug 2009 14:27:17 -0000</lastBuildDate><item><title>Re: A Quick Guide to DRYML</title><link>(u'http://hobocentral.net/blog/2006/11/10/guide-to-dryml/',%20779540329L)#comment-779540329</link><description>&lt;p&gt;I am not convinced. From what I understand, these custom tags are like functions - you define them, reuse them and they can take parameters. We had helpers all this time for that! Why reinvent the wheel just to replace Ruby methods with XML-like markup?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">mislav</dc:creator><pubDate>Mon, 25 Dec 2006 11:59:35 -0000</pubDate></item><item><title>Re: A Quick Guide to DRYML</title><link>(u'http://hobocentral.net/blog/2006/11/10/guide-to-dryml/',%20779540332L)#comment-779540332</link><description>&lt;p&gt;Why the choice of underscores instead of dashes, then? ("ul-for", "object-link" ...)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">mislav</dc:creator><pubDate>Mon, 25 Dec 2006 20:56:44 -0000</pubDate></item><item><title>Re: Prototype 1.5.1 release candidate</title><link>(u'http://prototypejs.org/2007/03/09/prototype-1-5-1-rc1/',%2026905760L)#comment-26905760</link><description>&lt;p&gt;Gio, can’t guess. But if you read the big red message box above the comment form, you would know that &lt;a href="/contribute" rel="nofollow noopener" target="_blank" title="/contribute"&gt;bug reports should be sent to the tracker&lt;/a&gt; ;)&lt;/p&gt;&lt;p&gt;You’re passing &lt;code&gt;obj&lt;/code&gt; to the &lt;code&gt;up&lt;/code&gt; method? Is that a string? It should be :S&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">mislav</dc:creator><pubDate>Sun, 11 Mar 2007 09:30:00 -0000</pubDate></item><item><title>Re: New in Prototype trunk: DOM builder</title><link>(u'http://prototypejs.org/2007/05/12/dom-builder/',%2026905933L)#comment-26905933</link><description>&lt;p&gt;Jim: I stand corrected :)&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">mislav</dc:creator><pubDate>Mon, 14 May 2007 13:16:00 -0000</pubDate></item><item><title>Re: New in Prototype trunk: DOM builder</title><link>(u'http://prototypejs.org/2007/05/12/dom-builder/',%2026905934L)#comment-26905934</link><description>&lt;p&gt;(Forgot)&lt;/p&gt;&lt;p&gt;Tobie: not only Safari chokes on unquoted keywords. IE does so, too.&lt;/p&gt;&lt;p&gt;Eimantas: it is very much alike &lt;a href="http://scrip.aculo.us" rel="nofollow noopener" target="_blank" title="scrip.aculo.us"&gt;scrip.aculo.us&lt;/a&gt; Builder. The latter has 2 extra features: you can define children and you can dump the node methods in some scope so you can get DIV and similar methods if you prefer that syntax.&lt;/p&gt;&lt;p&gt;It would be fairly easy to add both features to Prototype. But, for now, this is only a minimal builder that covers two most critical features: creating nodes and setting attributes. Building an additional API on top of that would be a piece of cake (and possibly left to the user).&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">mislav</dc:creator><pubDate>Mon, 14 May 2007 13:27:00 -0000</pubDate></item><item><title>Re: Paginating special queries</title><link>(u'http://zargony.com/2007/07/21/paginating-special-queries',%2065776843L)#comment-65776843</link><description>&lt;p&gt;Nice writeup. But you didn't think outside the box when you went to use with_scope! Hop to ticket #66 to see what I meant.&lt;/p&gt;&lt;p&gt;Your writing style is really good, keep em coming, but please - put some more contrast on the design. When I'm reading your blog I feed blind :O&lt;br&gt;-----&lt;/p&gt;&lt;p&gt;---&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">mislav</dc:creator><pubDate>Sat, 21 Jul 2007 12:07:00 -0000</pubDate></item><item><title>Re: Paginating special queries</title><link>(u'http://zargony.com/2007/07/21/paginating-special-queries',%2065776881L)#comment-65776881</link><description>&lt;p&gt;You complain about scope_out not being supported. But what about this: &lt;a href="http://plugins.require.errtheblog.com/changesets/326" rel="nofollow noopener" target="_blank" title="http://plugins.require.errtheblog.com/changesets/326"&gt;http://plugins.require.errt...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">mislav</dc:creator><pubDate>Thu, 23 Aug 2007 13:08:00 -0000</pubDate></item><item><title>Re: Prototype 1.6.0 RC1: Changes to the Class and Event APIs, Hash rewrite, and bug fixes</title><link>(u'http://prototypejs.org/2007/10/16/prototype-1-6-0-rc1-changes-to-the-class-and-event-apis-hash-rewrite-and-bug-fixes/',%2026906181L)#comment-26906181</link><description>&lt;p&gt;Ah, “at”-signs were interpreted incorrectly in my previous comment. Just ignore them.&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">mislav</dc:creator><pubDate>Wed, 17 Oct 2007 05:43:00 -0000</pubDate></item><item><title>Re: Prototype 1.6.0 RC1: Changes to the Class and Event APIs, Hash rewrite, and bug fixes</title><link>(u'http://prototypejs.org/2007/10/16/prototype-1-6-0-rc1-changes-to-the-class-and-event-apis-hash-rewrite-and-bug-fixes/',%2026906186L)#comment-26906186</link><description>&lt;p&gt;&lt;b&gt;Kniaź:&lt;/b&gt; No problem, wanting to help is always positive. &lt;a href="http://groups.google.com/group/prototype-core/t/db31803aafa510a8?hl=en" rel="nofollow noopener" target="_blank" title="http://groups.google.com/group/prototype-core/t/db31803aafa510a8?hl=en"&gt;We will definitely solve the Template issue&lt;/a&gt;, until then be sure to call “toObject()” when passing Hash data to your templates.&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">mislav</dc:creator><pubDate>Wed, 17 Oct 2007 06:37:00 -0000</pubDate></item><item><title>Re: Prototype 1.6.0 RC1: Changes to the Class and Event APIs, Hash rewrite, and bug fixes</title><link>(u'http://prototypejs.org/2007/10/16/prototype-1-6-0-rc1-changes-to-the-class-and-event-apis-hash-rewrite-and-bug-fixes/',%2026906192L)#comment-26906192</link><description>&lt;p&gt;Luis-&lt;/p&gt;&lt;p&gt;This is a major release we are speaking of, and APIs usually change in major releases. If you don’t want to change your old code you might scroll up to see one of my comments mentioning a blog post. I don’t really recommend it, though; it’s better to be safe with current Hash and getters/setters.&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">mislav</dc:creator><pubDate>Wed, 17 Oct 2007 07:51:00 -0000</pubDate></item><item><title>Re: Prototype 1.6.0 RC1: Changes to the Class and Event APIs, Hash rewrite, and bug fixes</title><link>(u'http://prototypejs.org/2007/10/16/prototype-1-6-0-rc1-changes-to-the-class-and-event-apis-hash-rewrite-and-bug-fixes/',%2026906195L)#comment-26906195</link><description>&lt;p&gt;Zuzmic: you might want to smack yourself on the head first and write &lt;code&gt;new Element(‘div’).setStyle({ opacity: 0.5})&lt;/code&gt; :)&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">mislav</dc:creator><pubDate>Wed, 17 Oct 2007 08:19:00 -0000</pubDate></item><item><title>Re: Prototype 1.6.0 RC1: Changes to the Class and Event APIs, Hash rewrite, and bug fixes</title><link>(u'http://prototypejs.org/2007/10/16/prototype-1-6-0-rc1-changes-to-the-class-and-event-apis-hash-rewrite-and-bug-fixes/',%2026906202L)#comment-26906202</link><description>&lt;p&gt;Woil: Tobie wanted to get true privacy for that object, but it would require jumping through hoops. I like it exposed, on the other hand, because I can access it in subclasses.&lt;/p&gt;&lt;p&gt;It’s &lt;b&gt;definitely&lt;/b&gt; bad practice to access that object directly in app code. The underscore (“pseudo-privacy”) is an indicator of that.&lt;/p&gt;&lt;p&gt;Mike Rumble: nice demonstration! I’m pleased to see that at least somebody started to notice benefits of this approach.&lt;/p&gt;&lt;p&gt;BTW, you must be registered to the (Freenode) services before talking to Pastie bot. After that, just say hi to Pastie &lt;b&gt;in public&lt;/b&gt; (“pastie: hi”).&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">mislav</dc:creator><pubDate>Wed, 17 Oct 2007 17:42:00 -0000</pubDate></item><item><title>Re: IM Integration With XMPP4r : Part 2</title><link>(u'http://www.rubyfleebie.com/im-integration-with-xmpp4r-part-2/',%2050352210L)#comment-50352210</link><description>&lt;p&gt;Frank,&lt;/p&gt;&lt;p&gt;It's great that you're writing about this. Both were excellent articles and I hope you'll keep it up.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">mislav</dc:creator><pubDate>Mon, 04 Feb 2008 00:32:25 -0000</pubDate></item><item><title>Re: Pratik joins core, retired members go alumni</title><link>('https://disqus.com/home/discussion/ridingrailsweblog/pratik_joins_core_retired_members_go_alumni_37/',%20456568051L)#comment-456568051</link><description>&lt;p&gt;Go lifo! WohohooO!!1&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">mislav</dc:creator><pubDate>Wed, 26 Mar 2008 21:09:00 -0000</pubDate></item><item><title>Re: Pratik joins core, retired members go alumni</title><link>(u'http://weblog.rubyonrails.org/2008/3/26/pratik-joins-rails-core-retired-members-go-alumni/',%20456768892L)#comment-456768892</link><description>&lt;p&gt;Go lifo! WohohooO!!1&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">mislav</dc:creator><pubDate>Wed, 26 Mar 2008 21:09:00 -0000</pubDate></item><item><title>Re: Import Gmail Contacts using Ruby on Rails</title><link>(u'http://blog.adsdevshop.com/2008/04/18/import-gmail-contacts-using-ruby-on-rails/',%2020756137L)#comment-20756137</link><description>&lt;p&gt;Or, simply use the Google Contacts Data API implemented in Ruby: &lt;a href="http://github.com/mislav/contacts/tree/master" rel="nofollow noopener" target="_blank" title="http://github.com/mislav/contacts/tree/master"&gt;http://github.com/mislav/co...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">mislav</dc:creator><pubDate>Wed, 23 Apr 2008 16:30:28 -0000</pubDate></item><item><title>Re: Phusion Passenger 2.0.5 now compatible with Edge Rails</title><link>('https://disqus.com/home/discussion/ridingrailsweblog/phusion_passenger_205_now_compatible_with_edge_rails/',%20456570351L)#comment-456570351</link><description>&lt;p&gt;We wanted to see how much better Passenger performs than our mongrels behind nginx, so I switched over our staging environment to it:&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;	&lt;/p&gt;&lt;p&gt;1) god stop mongrels; 2) stop nginx; 3) install apache2; 4) install passenger gem; 5) configure apache to load passenger module and to know where the application is; 6) reload apache. Done.&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;	&lt;/p&gt;&lt;p&gt;I then benchmarked the &lt;strong&gt;slowest&lt;/strong&gt; page of our app using the concurrency level of 50 and got a stable 60 reqs/sec. Memory usage was half of what Mongrels would use, and we’re not even running Enterprise Ruby.&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;	&lt;/p&gt;&lt;p&gt;A win.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">mislav</dc:creator><pubDate>Fri, 05 Dec 2008 13:01:00 -0000</pubDate></item><item><title>Re: Phusion Passenger 2.0.5 now compatible with Edge Rails</title><link>(u'http://weblog.rubyonrails.org/2008/12/5/phusion-passenger-2-0-5-now-compatible-with-edge-rails/',%20456771361L)#comment-456771361</link><description>&lt;p&gt;We wanted to see how much better Passenger performs than our mongrels behind nginx, so I switched over our staging environment to it:&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;	&lt;/p&gt;&lt;p&gt;1) god stop mongrels; 2) stop nginx; 3) install apache2; 4) install passenger gem; 5) configure apache to load passenger module and to know where the application is; 6) reload apache. Done.&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;	&lt;/p&gt;&lt;p&gt;I then benchmarked the &lt;strong&gt;slowest&lt;/strong&gt; page of our app using the concurrency level of 50 and got a stable 60 reqs/sec. Memory usage was half of what Mongrels would use, and we’re not even running Enterprise Ruby.&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;	&lt;/p&gt;&lt;p&gt;A win.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">mislav</dc:creator><pubDate>Fri, 05 Dec 2008 13:01:00 -0000</pubDate></item><item><title>Re: Hosting Ruby on Rails with Passenger</title><link>('https://disqus.com/home/discussion/ridingrailsweblog/hosting_ruby_on_rails_with_passenger/',%20456570425L)#comment-456570425</link><description>&lt;p&gt;I wrote an almost automated script that sets up Apache2 with Passenger and &lt;span&gt;REE&lt;/span&gt; on Ubuntu: &lt;a href="http://gist.github.com/32917—saved" rel="nofollow noopener" target="_blank" title="http://gist.github.com/32917—saved"&gt;http://gist.github.com/3291...&lt;/a&gt; me a lot of time.&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;	&lt;/p&gt;&lt;p&gt;@Andy: Passenger instances happen to run in an environment that can be different than the one in your console. That probably screws up your &lt;span&gt;GEM&lt;/span&gt;_HOME.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">mislav</dc:creator><pubDate>Tue, 16 Dec 2008 12:12:00 -0000</pubDate></item><item><title>Re: Hosting Ruby on Rails with Passenger</title><link>(u'http://weblog.rubyonrails.org/2008/12/16/hosting-ruby-on-rails-with-passenger/',%20456771445L)#comment-456771445</link><description>&lt;p&gt;I wrote an almost automated script that sets up Apache2 with Passenger and &lt;span&gt;REE&lt;/span&gt; on Ubuntu: &lt;a href="http://gist.github.com/32917—saved" rel="nofollow noopener" target="_blank" title="http://gist.github.com/32917—saved"&gt;http://gist.github.com/3291...&lt;/a&gt; me a lot of time.&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;	&lt;/p&gt;&lt;p&gt;@Andy: Passenger instances happen to run in an environment that can be different than the one in your console. That probably screws up your &lt;span&gt;GEM&lt;/span&gt;_HOME.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">mislav</dc:creator><pubDate>Tue, 16 Dec 2008 12:12:00 -0000</pubDate></item><item><title>Re: Cucumber steps for testing page URLs and redirects</title><link>(u'http://log.openmonkey.com/post/83273403',%207029442L)#comment-7029442</link><description>&lt;p&gt;We use &lt;a href="http://gist.github.com/76330" rel="nofollow noopener" target="_blank" title="http://gist.github.com/76330"&gt;http://gist.github.com/76330&lt;/a&gt;&lt;/p&gt;&lt;p&gt;Is testing redirects really necessary? Seems to me like something that belongs to functional tests, not acceptance. You should be able to change a redirect without any impact to the user.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">mislav</dc:creator><pubDate>Mon, 09 Mar 2009 10:32:30 -0000</pubDate></item><item><title>Re: Prototype 1.6.1 RC2: IE8 compatibility, Element storage, and bug fixes</title><link>(u'http://prototypejs.org/2009/03/27/prototype-1-6-1-rc2-ie8-compatibility-element-storage-and-bug-fixes/',%2026906588L)#comment-26906588</link><description>&lt;p&gt;Element storage and mouseenter/leave — simply wow! Great to see it got in at last&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">mislav</dc:creator><pubDate>Fri, 27 Mar 2009 20:05:00 -0000</pubDate></item><item><title>Re: 6 Steps To Refactoring Rails (for Mere Mortals)</title><link>(u'https://blog.engineyard.com/2009/6-steps-to-refactoring-rails-for-mere-mortals',%20156798224L)#comment-156798224</link><description>&lt;p&gt;Step 7: merge yourself with another master developer to form a superpowered human being named Carlhuda and leave a fire trail on your keyboard while hacking&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">mislav</dc:creator><pubDate>Mon, 29 Jun 2009 17:25:45 -0000</pubDate></item><item><title>Re: Wonderland &amp;mdash; Semantic List Markup with will_paginate</title><link>(u'http://blog.leshill.org/blog/2009/06/27/semantic-list-markup-with-will-paginate.html',%2013135366L)#comment-13135366</link><description>&lt;p&gt;You're not the first or the last to create this sort of patch or renderer. I was probably the first to consider this more than a year ago when I was first rewriting will_paginate published by PJ Hyett. In the end I didn't make it because of several reasons: 1) when the pagination is unstyled it spans vertically, which is pretty ugly; 2) screen readers for blind might pay too much attention to the list thinking it's content; 3) the ellipsis ("...") marked up as a list item is totally unsemantic, but there's no other option.&lt;/p&gt;&lt;p&gt;If you care about semantics that much, you should have used an OL instead of UL.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">mislav</dc:creator><pubDate>Wed, 22 Jul 2009 18:27:20 -0000</pubDate></item><item><title>Re: Blossom the lovely stars, the forget-me-nots of the angels</title><link>(u'http://robots.thoughtbot.com/post/164115286',%2014967502L)#comment-14967502</link><description>&lt;p&gt;I'd vote the Google way: "remember me" unchecked by default, but there's a cookie that remembers the checked state long after the "remember" cookie has expired. That way you only have to choose "remember me" setting once per computer.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">mislav</dc:creator><pubDate>Mon, 17 Aug 2009 14:27:17 -0000</pubDate></item></channel></rss>