Comments on: Project Website, Part Two: Simple jQuery With Rails http://www.pathf.com/blogs/2008/07/project-website-part-two-simple-jquery-with-rails/ Running commentary about agile development, user experience design and Ajax. Fri, 05 Dec 2008 07:53:12 +0000 http://wordpress.org/?v=2.5.1 By: Pathfinder Development » Project Website Part 4: Drag and Drop in jQuery http://www.pathf.com/blogs/2008/07/project-website-part-two-simple-jquery-with-rails/#comment-2627 Pathfinder Development » Project Website Part 4: Drag and Drop in jQuery Fri, 25 Jul 2008 17:12:28 +0000 http://www.pathf.com/blogs/?p=1036#comment-2627 [...] you may recall from the last jQuery post, the $(function() setup allows all the code in that function to be executed when the page DOM has [...] [...] you may recall from the last jQuery post, the $(function() setup allows all the code in that function to be executed when the page DOM has [...]

]]> By: Andrew Vit http://www.pathf.com/blogs/2008/07/project-website-part-two-simple-jquery-with-rails/#comment-2487 Andrew Vit Thu, 17 Jul 2008 21:27:27 +0000 http://www.pathf.com/blogs/?p=1036#comment-2487 @Glenn: agree with you on Prototype.js & the built-in helpers... I've been using the LowPro extension to Prototype for a while now, and it addresses all of the unobtrusiveness shortcomings of Prototype really well. To be honest, I haven't played with jQuery yet, but with LowPro I don't really see any reason to ditch Prototype. In fact, I would love to see LowPro's behavior merged into Prototype as a core feature (it's tiny), and perhaps update the rails helpers for it (though I don't use the RJS helpers myself either). @Glenn: agree with you on Prototype.js & the built-in helpers… I’ve been using the LowPro extension to Prototype for a while now, and it addresses all of the unobtrusiveness shortcomings of Prototype really well. To be honest, I haven’t played with jQuery yet, but with LowPro I don’t really see any reason to ditch Prototype. In fact, I would love to see LowPro’s behavior merged into Prototype as a core feature (it’s tiny), and perhaps update the rails helpers for it (though I don’t use the RJS helpers myself either).

]]> By: masone http://www.pathf.com/blogs/2008/07/project-website-part-two-simple-jquery-with-rails/#comment-2452 masone Wed, 16 Jul 2008 12:15:31 +0000 http://www.pathf.com/blogs/?p=1036#comment-2452 Thanks for that introduction! I'm just diving into Jquery and Unobtrusive Javascript. I think that this whole content_for :jquery stuff is quite repetitive and unnecessary. So I wrote a plugin which automatically includes the corresponding Javascript in the HTML header if a js.erb template is found. It's located here: http://github.com/masone/js.erb-auto-include-plugin/tree/master I'd be glad to hear what other people think about it since I'm not really experienced in that area :) Thanks for that introduction! I’m just diving into Jquery and Unobtrusive Javascript.

I think that this whole content_for :jquery stuff is quite repetitive and unnecessary. So I wrote a plugin which automatically includes the corresponding Javascript in the HTML header if a js.erb template is found.

It’s located here:
http://github.com/masone/js.erb-auto-include-plugin/tree/master

I’d be glad to hear what other people think about it since I’m not really experienced in that area :)

]]> By: Glenn http://www.pathf.com/blogs/2008/07/project-website-part-two-simple-jquery-with-rails/#comment-2436 Glenn Tue, 15 Jul 2008 22:23:45 +0000 http://www.pathf.com/blogs/?p=1036#comment-2436 Great article, and your conclusions are pretty much what I'd come to understand myself. And the cons alone are almost enough to make me switch, yes the cons. The built in rails helpers are absolutely awful in terms of developing an accessible site using progressive improvement with unobtrusive JS (buzzword bingo! I win). They promote all kinds of bad habits, so I'd happily ditch them... well I already have. if jQuery makes the javascript coding even easier than prototype/scriptaculous, then it probably should become the new defacto standard. Thanks again Great article, and your conclusions are pretty much what I’d come to understand myself. And the cons alone are almost enough to make me switch, yes the cons. The built in rails helpers are absolutely awful in terms of developing an accessible site using progressive improvement with unobtrusive JS (buzzword bingo! I win). They promote all kinds of bad habits, so I’d happily ditch them… well I already have. if jQuery makes the javascript coding even easier than prototype/scriptaculous, then it probably should become the new defacto standard.

Thanks again

]]>