Comments on: From JSP to Ruby on Rails: First thoughts on front-end coding conventions http://www.pathf.com/blogs/2008/11/from-jsp-to-ruby-on-rails-first-thoughts-on-front-end-coding-conventions/ Running commentary about agile development, user experience design and Ajax. Fri, 05 Mar 2010 19:33:43 -0600 http://wordpress.org/?v=2.8.4 hourly 1 By: charlie bowman http://www.pathf.com/blogs/2008/11/from-jsp-to-ruby-on-rails-first-thoughts-on-front-end-coding-conventions/comment-page-1/#comment-4101 charlie bowman Wed, 12 Nov 2008 16:15:54 +0000 http://www.pathf.com/blogs/?p=1253#comment-4101 One solution I've used is to create a presenter for each one of the displayable models. Each presenter can follow the same inheritance structure as the model and can really help to clean up those nasty helper methods. One solution I’ve used is to create a presenter for each one of the displayable models. Each presenter can follow the same inheritance structure as the model and can really help to clean up those nasty helper methods.

]]> By: Piotr Sarnacki http://www.pathf.com/blogs/2008/11/from-jsp-to-ruby-on-rails-first-thoughts-on-front-end-coding-conventions/comment-page-1/#comment-4095 Piotr Sarnacki Wed, 12 Nov 2008 10:13:02 +0000 http://www.pathf.com/blogs/?p=1253#comment-4095 About javascript. I think that creating accessible and unobtrusive apps with ajax is a matter of not mixing javascript code and view code. So anyway, I don't use rails helpers at all. I try not to use rails js callbacks either, for keeping my javascript out of rails. But this one isn't necessary for unobtrusive app. About javascript. I think that creating accessible and unobtrusive apps with ajax is a matter of not mixing javascript code and view code. So anyway, I don’t use rails helpers at all.

I try not to use rails js callbacks either, for keeping my javascript out of rails. But this one isn’t necessary for unobtrusive app.

]]> By: JONNALAGADDA Srinivas http://www.pathf.com/blogs/2008/11/from-jsp-to-ruby-on-rails-first-thoughts-on-front-end-coding-conventions/comment-page-1/#comment-4093 JONNALAGADDA Srinivas Wed, 12 Nov 2008 05:23:57 +0000 http://www.pathf.com/blogs/?p=1253#comment-4093 Nice analysis! On a couple of reasonably large Ruby on Rails projects (over 100,000 lines of Ruby code), I have seen views accumulate business logic inseparably. For comparison, liftweb has "views with no controller/model logic" as one of its core principles. DPP admits, though, that the opposite (view logic creeping into controller) is more difficult to stop. Nice analysis! On a couple of reasonably large Ruby on Rails projects (over 100,000 lines of Ruby code), I have seen views accumulate business logic inseparably. For comparison, liftweb has “views with no controller/model logic” as one of its core principles. DPP admits, though, that the opposite (view logic creeping into controller) is more difficult to stop.

]]> By: Robert Pierce http://www.pathf.com/blogs/2008/11/from-jsp-to-ruby-on-rails-first-thoughts-on-front-end-coding-conventions/comment-page-1/#comment-4078 Robert Pierce Tue, 11 Nov 2008 07:55:04 +0000 http://www.pathf.com/blogs/?p=1253#comment-4078 Hi Brian, thanks for an interesting, insightful writeup. It sounds like you may find haml/sass/blueprintcss useful/delightful in your further Rails travels. Haml/Sass: http://haml.hamptoncatlin.com/ Compass(blueprint integration): http://github.com/chriseppstein/compass/tree/master Hi Brian, thanks for an interesting, insightful writeup. It sounds like you may find haml/sass/blueprintcss useful/delightful in your further Rails travels.

Haml/Sass: http://haml.hamptoncatlin.com/
Compass(blueprint integration): http://github.com/chriseppstein/compass/tree/master

]]>