Hey there, I use the admin generator exclusively for my admin backends. I find that it gives a quick yet solid foundation for all my admin needs, and if I run into situations like you describe (make the same changes to different modules) I can simply extend the generator itself and the changes take effect elsewhere. Also, by not generating a "solid module" you keep yourself open for future improvements, as has just happened within the Propel15 admin generator for example.
I agree that the generator.yml can be abused, but I only use it as an optional control layer on top of what the forms do by default, so there's not much duplication. Does that help, or am I misunderstanding the issue? Daniel On Jul 26, 11:31 am, andromeda lights <andromedalig...@gmail.com> wrote: > Yes, Christian, > > I used admin generator like you. It is not real required. Maybe useful for > code generation without any effort. > > Ertan Kayalar > php & .net developer > > 24Saat Web Hizmetleri > > www.erkasoft.com<http://www.erkasoft.com%20/>www.webtasarimsitesi.comwww.24saat.netwww.ertankayalar.com.tr > > 2010/7/26 Christian Fazzini <christian.fazz...@gmail.com> > - Alıntılanan metni göster - > > 2010/7/26 Christian Fazzini <christian.fazz...@gmail.com> > > > Hello all, > > > I've used admin generator a few times. Personally, I don't really > > understand the point of this. The forms in admin generator are based > > on the definitions in the form class. For the backend app, why is the > > common convention for devs to use admin generator? The only difference > > admin generator provides is the search filter. Doctrine generate > > creates the same kind of CRUD functionality that is seen in admin > > generator. > > > Second, since we have to rely on yml files (i.e. generator.yml) to > > configure the forms in admin generator. It leads to messy code. > > Especially when we have to declare partials in the .yml file just to > > display something different. > > > Third, if our forms are a bit more complex. We need to copy most of > > the code from /cache dir and paste into the backend module actions > > file. Which makes it a bit tedious if we need to extend our > > application. Plus, we need to do this for every backend module that > > admin generator creates. And the same thing for templates! > > > If I would have used doctrine generate (for example: symfony > > doctrine:generate-module --with-show --non-verbose-templates frontend > > user User) instead. I would have easy access to the templates folder. > > and the action files. Exactly the same way I would have it in the > > frontend app. Which in some ways, also keeps the coding structure > > consistent. > > > Having admin generator only complicates the flow of things and defeats > > the purpose of keeping things convenient. > > > I am starting to suspect that the admin generator is more for > > prototyping than anything.... > > > What are your thoughts? > > > -- > > If you want to report a vulnerability issue on symfony, please send it to > > security at symfony-project.com > > > You received this message because you are subscribed to the Google > > Groups "symfony users" group. > > To post to this group, send email to symfony-users@googlegroups.com > > To unsubscribe from this group, send email to > > symfony-users+unsubscr...@googlegroups.com<symfony-users%2bunsubscr...@googlegroups.com> > > For more options, visit this group at > >http://groups.google.com/group/symfony-users?hl=en -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en
