Curtis Cooley wrote: > On Mon, Jan 11, 2010 at 9:57 PM, Ritchie <ritch...@gmail.com> wrote: >> GET and should display a form. It shouldn't be updating anything. >> >> This guide should set you on the right track: >> http://guides.rubyonrails.org/getting_started.html >> > > Ok, so the recipe allows you to replace 4 similar methods with one > method, which is more DRY, but from what Ritchie is saying, adhering > to the RESTful interface is more important. > > Is it 'better' to keep the four methods and DRY them up as best I can > rather than trying the post back method recipe? I'm thinking so, since > the post back recipe made me do some things I didn't really like, like > removing the resources entry from my routes. And it broke things. > > Plus, I just discovered that the "Rails Recipes" book is for Rails > 1.0. Sheesh, I just bought it :( > > Perhaps the post back model isn't encouraged any more despite it's > DRYness.
Yeah, this looks like a mediocre idea. If you want to avoid repetition in your controllers, I'd suggest something like make_resourceful. > -- > Curtis Cooley > curtis.coo...@gmail.com > home:http://curtiscooley.com > blog:http://ponderingobjectorienteddesign.blogspot.com > =============== > Leadership is a potent combination of strategy and character. But if > you must be without one, be without the strategy. > -- H. Norman Schwarzkopf Best, -- Marnen Laibow-Koser http://www.marnen.org mar...@marnen.org -- Posted via http://www.ruby-forum.com/.
-- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-t...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
