Agreeing with José, I work on a University, and we try to keep all our systems follow a pattern, so clients get used to our layout and design and our developers get standard comment tips about how to name and describe methods. For this, we rely strongly on scaffold customization.
I also agree that this should not be put as an advantage for beginners on tutorials and books, showing them how to "not" write code. Even a warning message could appear on scaffolding generation, or making the generators a little less "automagic" (and maybe a little more dumb also), forcing people to customize scaffolds before getting something usable. I believe that with this aproach, we can change the maintenance cost of keeping the scaffold generators up to date from the core developers who would not need to firstly update generators, to the experienced developers who contribute to rails on every realease candidate. -- Att, Everton -- 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.
