Scaffolding adds things you may or may not want. It's an easy starting point. Sometimes I use it when I need a very simple crud interface. BUT I never use much of the generated views and I'm careful to delete the bits I don't want and change the rest. It also saves a tiny amount of effort to generate the scaffold and do a quick add to my repository. Nothing gets forgotten that way.
I've noticed that a lot of beginners seem to get in trouble with scaffolding. They don't necessarily know what all the pieces generated are or how they fit together, so they don't know what needs changed or what needs deleted. So they end up with effects they don't understand. For beginners I would recommend coding from the ground up by hand until they reach the level where they KNOW what the scaffold will produce and how closely it resembles what they really want. On Nov 25, 4:59 am, Ralph Wood <[EMAIL PROTECTED]> wrote: > For every tutorial that uses scaffolding, there's an article that says > you shouldn't use it in real websites. Supposedly it just serves to > "sketch things out quickly", "test database connectivity" and other > stuff. Some say you're not even supposed to use it and then edit it > later. I don't get why. > > What is it about scaffolding that makes it virtually useless? It > generates some code; surely I could just expand on it or "fix" what's > wrong with it later, right? Apparently not. How is it different from me > making my own CRUD base files and copypasting it into every project? > > I just don't get it. > -- > Posted viahttp://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 [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-talk?hl=en -~----------~----~----~----~------~----~------~--~---
