On 3/2/07, Jeff <[EMAIL PROTECTED]> wrote: > > On Mar 2, 5:45 am, "Wayne E. Seguin" <[EMAIL PROTECTED]> wrote: > > On Mar 02, 2007, at 00:33 , Dave Thomas wrote: > > > > > It can be useful for the maintenance of things like lookup tables, > > > particularly during development. > > > > > Dave > > > > True, but this can just as easily be facilitated as a plugin. > > > > ~Wayne > > > What was meant by 'dynamic' scaffolding? If we're talking about > removing the scaffold generator, then I'm against it. Many people > learn a lot from generating the scaffolding for a controller and then > reading the generated code. I'd hate to make them learn how to > install plugins first. > > If you're instead referring to the 'scaffold' class method that can be > used in a controller, then I'm all for removing it :-) > > Jeff > softiesonrails.com
Big plus +1 here. Dynamic scaffold == bad. Static == very good for newbies and learning. - rob --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
