Ruby on Rails: RESTful scaffolds, .rhtml/.rxml deprecation, and form_for( @modelname ) syntax; oh my!

I’m a newbie to Ruby on Rails. Delirious and unphased, I decided to compound this precarious position by writing my first Rails web app using Edge rails instead of the standard 1.2.x build. Three things have confused me to this point, and I’m sure more are to come. If you’re using Edge Rails, here’s hoping I can save you a few moments of frustration:

• script/generate scaffold_resource model_name (the command given in the REST Peepcode to generate a scaffold for a RESTful resource), no longer works. Instead, do this: script/generate scaffold model_name.
• When I finally did get a RESTful scaffold going, the view files for the various controller actions were given file names such as “edit.html.erb” instead of “edit.rhtml” as I was expecting. This is because .rhtml has been deprecated in Rails 2.0 (I guess because, since edit.rhtml isn’t strictly HTML, it shouldn’t have a file name that makes it look like it is; I’m not sure I buy this, but that’s the way the Rails file extensions crumble, kids). As a side-note, “.rxml” files are also deprecated in favor of “.builder” files.
• Finally, in this new “edit.html.erb” view file, I noticed that the form_for declaration looks like this: <% form_for(@modelname) do |f| %>. I had never seen this form_for syntax documented anywhere, so I proceeded to rant and rave and beat my head against the wall for awhile before I searched my own project in Textmate, and noticed that the Edge Rails CHANGELOG contained this note:
  

  * Added record identifications to FormHelper#form_for and PrototypeHelper#remote_form_for [DHH]. Examples:

  <% form_for(@post) do |f| %>
  …
  <% end %>

  This will expand to be the same as:

  <% form_for :post, @post, :url => post_path(@post), :html => { :method => :put, :class => “edit_post”, :id => “edit_post_45″ } do |f| %>
  …
  <% end %>