Red Squirrel Reflections
Dave Hoover explores the psychology of software development

Dave Hoover

All [Atom]
Craftsmanship [Atom]
Dynamic [Atom]
Intersection [Atom]
Learning [Atom]
Links [Atom]
Polyglot [Atom]
Projects [Atom]
XP [Atom]
Old Blog

Obtivian Blogs

Andy Maleh
Colin Harris
Fred Polgardy
Jim Breen
Kevin Taylor
Todd Webb
Turner King
Tyler Jennings


March 2009 (1)
January 2009 (1)
December 2008 (1)
October 2008 (3)
September 2008 (1)
June 2008 (4)
April 2008 (3)
March 2008 (1)
February 2008 (1)
August 2007 (1)
July 2007 (1)
June 2007 (1)
May 2007 (4)
April 2007 (3)
March 2007 (5)
February 2007 (6)
January 2007 (6)
December 2006 (10)
November 2006 (5)
October 2006 (8)
September 2006 (8)
August 2006 (5)
July 2006 (12)
June 2006 (7)
May 2006 (5)
April 2006 (5)
March 2006 (4)
February 2006 (2)
January 2006 (5)
December 2005 (5)
November 2005 (3)
October 2005 (3)
September 2005 (6)
August 2005 (4)
July 2005 (7)
June 2005 (14)
May 2005 (6)
April 2005 (8)
March 2005 (9)
February 2005 (11)
January 2005 (16)
Old Archives


Fri, 24 Mar 2006

Using Rails as Javascript Scaffolding

I'm working on something that I'm not talking about yet, but I can say it's a Rails app. I'm likely a bit behind the times, but I thought I'd mention a habit emerging in my Rails/Ajax development that I haven't read about in any of the blogs I follow.

After I started playing with Behaviour, I grew to appreciate keeping my markup free of Javascript. At the same time, I enjoy using Rails JavaScriptHelper methods to do the dirty work for me. So what I end up doing is writing the Rails code and get everything working the way I want it. Then I view source in my browser, copy the Rails-generated HTML and Javascript and paste over the Rails code in my template. Then I'm free to separate everything into the appropriate places. Styles can get pulled up into a CSS file, onFoo methods can get extracted into Behaviours, and HTML elements can be formatted and identified the way I want. I just went through this routine with the marvelous autocomplete and it worked like a charm.

It feels so right, I wonder if it's wrong. I suppose I'm making my code more susceptible to breaking with future Rails/Scriptaculous upgrades. But it also feels like a smaller incarnation of the Rails scaffolding philosophy. So I'm wondering if I'm just doing something many others have silently practiced before me or if I'm violating an unspoken rule of Rails development.

[/projects/beratings] permanent link

powered by blosxom