I see the admin generator more as a starting point, something you can
build upon.
We have in our application backend both simple and complicated admin
modules.
Simple - generated admin modules where only a couple of partials are
used, no actions override.
Complicated - rewritten editing + custom object actions.
Even for complicated modules we are able to reuse some functionality
such as listing, filtering, ordering
so it's a win for my point of view.
What I've seen also in our project is that people don't know how to
solve a given task using the admin generator
and start to work "against it" (due to time constraints, other
reasons) thus defeating the whole point of using it.
Having less lines of written PHP code is always good.
gabriel
On Jul 26, 9:03 pm, Christian Fazzini <christian.fazz...@gmail.com>
wrote:
> 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
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en
