Scaffold Generator Woes

rubyonrails-core
41

I wasn’t referring about custom scaffold generators.

I just said that it is pretty easy to customize the generators

templates for your needs:

http://guides.rubyonrails.org/generators.html#customizing-your-workflow-by-changing-generators-templates

Best,

Rodrigo.
42

I wasn’t sure where to jump into this thread, but my vote is to keep the generator since it is a helpful “canonical example” for those trying to get started.

However, I do suggest one change, that might sound a bit radical, but which I think supports most of the thinking I’m seeing in this thread: rename the generator to something that makes it clear it’s more for educational purposes than anything else.

Something like “example_resource” might make it really, really obvious that the code is an example, shows all the possible actions, even has a couple of responders, etc… basically a way to see a good example of both code and forms that follow all of the naming conventions. But it’s clear it’s just an example and not simply a real starting point.

$ rails g example_resource Product title sku

Of course, it is a real starting point for those of us who understand Rails and use it like Jose does - we know how to customize what we want - but for those new to Rails it’s clear it’s just an example to help them understand the possibilities and get familiar with the conventions.

I think also getting the name “resource” in there helps normalize our vocabulary a bit more instead of “scaffold” which isn’t really used anywhere else in the framework.

Jeff

43

I'm in agreement here. Renaming to prefix with example_ would solve two issues. First, it would explicitly show it to be an example and having to type that would reinforce that. Second, by also adding a statement to the very top of each generated file via some header addition would also help reinforce that. A statement that this is just to give them an idea should suffice.

44

Hello Friends,

I am, Nyoman, a new bie from Bali, Indonesia.

For me, nothing is wrong to have scaffold. Why?

  1. By having the scaffold, I have a ‘mirror’ where I can see the flow of how the framework is working.
  2. When I try to do the same manually, I can easily see my mistakes of what made my app error.

So now it depends on the peoples themselves. If they are serious to learn and understand about the framework, then they will dig it into the deepest possible. If they want just to have a fun, then let they do it. You know, sometimes, people will learn further because it the beginning the framework gave him a good impression. Just like a man met good and beautiful girl…heeeeeeeee…

This is based on my personal learning experience, as what I am doing right now…

I wish every one of us to have good time during this year and have good learning of ROR…

Good luck…

45

Hi Duta,

I think this ship sailed about four years ago, and in general it’s not good mailing list etiquette to reply to very old threads.

But you were nice and well intentioned, so I moderated this through. Have a nice year too.

– Chad

46

And apparently google groups no longer provides the ‘reject with comment’ moderation option, which is why I handled like this. If any other group mods know how to you can still do that, please let me know…

– Chad