Admin Generator: Further enhancement beyond symfony's capability

Prev		Next

http://www.symfony-project.org/forum/index.php?t=msg&goto=33583&#msg_33583

I had always been wondering, how can I make use of the existing Admin Gen generated code, save and use them somewhere else, then twist it further which might beyond symfony's capability, or as the last step to arrange the input fields better, eg, group several entries on one line instead of spreading them vertically, etc.

Plese help/comment.

In the meantime, I notice an interesting topic going on at: http://www.symfony-project.org/forum/index.php?t=msg&th= 7947&start=0&

Which indicates that, there are at least 3 ways doing so:

twist directly in cache, which face the problem that the changes can be overwritten at any moment.
copy them to myapp/modules/module/template folder, and twist there.
or change theme if you want to make the changes happen automatically.

Furthermore, instead of the current list/edit actions, can we add our own actions, eg, view1, view2, so that we can have multiple views to the same module? Ref, currently the symfony AdminGen interface lacks the possibility to have multiple views to the same module (msg posted at http://www.symfony-project.org/forum/index.php?t=msg&th= 7705),

thanks

Admin Generator: Further enhancement beyond symfony's capability

I think you answered your first question yourself.

You can copy the files from cache to your module/template folder and alter them there.

If you want to have these changes in more than one module it is wise to change your theme instead.

About your second question, about I think a good solution is to create a second module for the same object, but give it an other name.

The command-line for that is simply

symfony propel-init-admin <app> <module-name-2> <object-name>

E.g., I have a module assignment and I created a new module assignment2 by only typing:

symfony propel-init-admin backend assignment2 Assignment

And when i browse to http://localhost/backend_dev.php/assignment2 it works immediately.

and edit your generator to match it for your other view, maybe change the actions.class.php file to redirect the edit action to the first module and change the actions.yml file of the first module to redirect you back to module2 once you have saved your changes.

An other solution for your second problem would be to add this capability in your theme as well. Which is probably even nicer.

documented on: 28 August 2007, lvanderree