Hey Christian, I guess I haven't really played with the non-admin-generator version of admin modules. However, I think Gustavo speaks to my point that so far the admin generator fits my requirements quite well. Specifically, for my work I build quite a lot of different apps and sites with symfony, and over time I'm responsible for keeping them up to date, so the more I can rely on code generation, the more I can ensure that all/most future updates and improvements get inherited natively. But yeah, I guess if I had fewer systems to maintain with more custom requirements, what you say makes sense. Thanks for the perspective.
Daniel On Aug 2, 6:24 pm, Christian Fazzini <christian.fazz...@gmail.com> wrote: > Yes but I think you are missing the point Richtermeister. All this > extending makes it more difficult with the admin generator involved. > Not difficult perse'. But just extra effort. If one can achieve the > same thing using just plain sfForm, why do we need to go through admin > generator to do the same thing, if not make things more complicated. I > dislike the fact that I have to rely on copying everything on cache to > extend admin gen. Second, to create simple columns in admin gen, I > have to use partials. And third, admin generator needs to be > configured via a yml file. > > All this can be done simply through sfForm. Much easier tasks, and > code is consistent. > > As Andromeda suggested. I am starting to think that admin generator is > more for prototyping (rapid development for show) than anything. > > On Jul 27, 4:07 am, Richtermeister <nex...@gmail.com> wrote: > > > 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/26ChristianFazzini<christian.fazz...@gmail.com> > > > - Alýntýlanan metni göster - > > > > 2010/7/26ChristianFazzini<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
