I think it depends on your requirements. If you need a backend with simple CRUD modules.. then you could use the generator to create them in just a few minutes. Maybe then customize the templates and there you go. You have a fully CRUD module ready to go in notime. You could of course extend the generator to use your own templates and then you could run the generator task and create a customized module even faster. I think it's great for typical CRUD modules, and not just for prototyping. I managed to fully customize its templates and now I use it on my CMS's a lot, and it makes me save a lot of time.
If you have a complex requirement for your backend then you'll have to do it on the normal way. But it's nice to have a tool like that to create CRUD modules fast enough to reduce your development time and focus on more complex tasks. My two cents. Cheers. On Mon, Aug 2, 2010 at 10:24 PM, Christian Fazzini < [email protected]> 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 <[email protected]> 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 <[email protected]> > > 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<[email protected]> > > > - Alýntýlanan metni göster - > > > > > 2010/7/26ChristianFazzini<[email protected]> > > > > > > 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 [email protected] > > > > To unsubscribe from this group, send email to > > > > [email protected]<symfony-users%[email protected]> > <symfony-users%[email protected]<symfony-users%[email protected]> > > > > > > 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 [email protected] > To unsubscribe from this group, send email to > [email protected]<symfony-users%[email protected]> > 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en
