On Mar 3, 7:40 pm, "Josh Peek" <[EMAIL PROTECTED]> wrote: > The plugin is a direct port, no new enhancements, even though it could > use some. O, and for the first time, scaffolding tests! >
I'm not maintaining it anymore, but I did create a full dynamic resource scaffolding plugin, last year, that you are welcome to borrow from, if there is anything worth it in there: http://code.google.com/p/dynamic-scaffold-resource/ . I followed the existing scaffolding code (that existed at that time, obviously), as closely as I could. After making that plugin I started to come around to the core team's views on the shortcomings of scaffolding, but I still don't like the lack of DRYness of how much shared code there is between my controllers. Maybe the generator should create a shared restcontroller to inherit from? Basically an updated version of http://geekonomics.blogspot.com/2006/07/crud-and-shared-controllers.html That allows for DRYness with the flexibility to easily override, customize, and extend. Not sure if there is any interest in doing so in core, so I went ahead and did so for my own use, but it's MIT licensed, so have at it. ;) I just think the move to REST simplifies things enough that they can be DRYed out even more. http://code.google.com/p/restcontroller/ http://www.timocracy.com/articles/2007/04/03/dynamic-scaffold-resource-is-dead-long-live-restcontroller --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
