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 On Sun, Jan 3, 2016 at 10:19 PM, Chad Woolley <thewoolley...@gmail.com> wrote: > 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 > > On Sun, Jan 3, 2016 at 8:16 PM, Duta Ksp <duta...@gmail.com> wrote: > >> 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.. >> >> >> >> >> On Friday, March 9, 2012 at 1:30:39 AM UTC+7, Ryan Bigg wrote: >>> >>> Hello friends, >>> >>> It's been fun having the scaffold generator exist as a part of Rails >>> since The Beginning Of Time, but I think its time is now up. It has been >>> abused time and time again, and most often leads to confusion amongst >>> people who are new to Rails. >>> >>> This confusion happens when a user first generates a scaffold and sees >>> that it is good. They can perform CRUD actions on a resource using one >>> command?! WOW! >>> >>> Then they try to modify the scaffold and run into problems. First of >>> all: how do they add an action to the controller? Do they need to run >>> another command? How do they then define a route for that action? A >>> template? >>> >>> If they were to *not* use the scaffold generator from the beginning, I >>> believe they would have less confusion. They would know how to add another >>> action to the controller and a template for that action because this would >>> be how they're doing it from the start. Learning how to define a route for >>> a new action in the controller is something easily learnable by reading the >>> routing guide. >>> >>> I think that we can fix this problem in one of two ways, the latter more >>> extreme than the first one. >>> >>> The first way is that we *completely change the Getting Started Guide >>> to simply *mention* the scaffold generator*, but then show people the >>> "correct" way of generating a controller (rails g controller) and adding >>> actions to it one by one, adding a model as its needed, and using similar >>> practices to how you would do it in the "real world". >>> >>> The second way, and sorry if this sounds a little extreme, is to *completely >>> remove the scaffold generator from the core of Rails* itself. This >>> means that there wouldn't even be the option to run the scaffold generator >>> for newbies. You could then extract this out into a gem if you *really* >>> wanted people to have the option for it. However, if this path was taken it >>> should be made clear that this is not the "sanctioned" way to create >>> controllers. >>> >>> Thoughts? >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Ruby on Rails: Core" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to rubyonrails-core+unsubscr...@googlegroups.com. >> To post to this group, send email to rubyonrails-core@googlegroups.com. >> Visit this group at https://groups.google.com/group/rubyonrails-core. >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-core+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-core@googlegroups.com. Visit this group at https://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/d/optout.
