Completely agree with the above. I was very close to give up on rails after spending a good 4 days trying to make my first application work. I was unfortunate enough to try rails after 2.02 was released. All of the documentation I found did not work. The beauty of ruby and rails keep me going. Finally I go it from blogs like yours and this one http://davidlynch.org/blog/2008/01/rails-20-scaffolding . Thanks!

http://wiki.rubyonrails.com/rails/pages/Scaffolding+Extensions+Plugin

http://wiki.rubyonrails.org/rails/pages/Scaffolding+Extensions+Tutorial

Sorry, it looks like we’re in the concrete from the get go same as if we’d done the generate static scaffold from 1.x.

Steven

I was using 1.x a few months ago, but 2.0 is starting to get as bad as Java

I may come back and pinch some ideas from you now (in moving from Rails 1.x to 2.x we should all stick together!)

As I’ve said elsewhere, I think ‘breaking’ the scaffold from 1.x to 2.x was a mistake. While the 2.x version may (arguably) be an ‘improvement’, it also breaks all the existing tutorials and puts barriers in the way of newcomers. Speaking as the developer of a Ruby On Rails IDE, I may also add that even tiny ‘breaks’ (anything from the syntax of a script to the naming conventions of files - ‘.rhtml’ to ‘html.erb’) also breaks the IDEs (and forces us to divert our efforts into fixing things that weren’t hirtherto broken rather than getting on with developing new features). While I can understand the attractions of re-designing a system such as Rails to be more aesthetically pleasing to the developer, I must admit to serious reservations about some of the changes made in Rails 2.0. I only hope this is a one-off…

best wishes
Huw Collingbourne