Agreed we should not have generated cache files, and that the controller extends a base class with most of the code (and action methods broken into several method calls so functionality can be tweaked without having to override the entire action method)
Here's a post I made about this a while ago: START POST Are there plans to get some input from the community on how this will be built? Seems like a great opportunity to build something world class. Sure we can take some inspiration from the Django admin, which is fairly neat (in terms of the coding etc.) Personally, I hope we don't have any more autoModelname_actions being generated, as I feel there are better ways of achieving the same result. (base templates can be generic to work for all admin generated modules, can be extended or replaced, generation can make main controller only, that would extend class like BaseAdminController etc.) I hope the community can embrace Twig here, as it would suit the admin well. Don't want to get into a template engine argument though - good that Symfony2 will be able to interweave e.g. a php template extending a Twig base template. People DO judge a book by its cover, so it would be good if the out the box style was top notch too. Who are our top designers who use symfony? Some gracefully degrading java script enhancements would be good too. Good to see the Symfony2 website looking a bit prettier than v1. This will help adoption too. I'd love to see an area set up where this can be discussed. Dev Community - what would you like to see in the new admin? Likes/ Dislikes of old admin? (http://groups.google.com/group/symfony-devs/browse_thread/thread/ a22aa37cd2625e8c/797342d711cbe7a4#797342d711cbe7a4) END POST If it's done correctly, it can also tie in to the CMF initiative. I'm hoping the new form framework and renderer will allow us to have forms with both soft tabs and fieldsets, highlighting tabs with errors etc. At the moment the rendering is so tied to the generated code it's impossible to render other bespoke admin code in a similar manner to the admin generated forms without building your own reuseable partials etc. I think we need to stop thinking about how the current admin generator stuff works completely, and think afresh. I'd also like people to think about: Menu Generation (multi level drop down - I use Superfish - http://users.tpg.com.au/j_birch/plugins/superfish/) Breadcrumbs and Hierarchy of Models and action e.g. Adding / Editing Room Types only once you have navigated to an Accommodation Every entity should really have a "show" action or "view" action. e.g. for the above example, the view page of an accommodation may be like: Hotel de Chateau rooms: 10 soming: yes Room Types *no room types* [add new room type] Facilities pool wifi [manage facilities] Also, image management for entities needs improved. I always like to have several actions associated with editing an entity. e.g. for an accommodation the actions are: Properties (main edit form) Policies Facilities Primary Images Image Gallery Room Types (leads to the editing of room types that belong to the Accommodation) Ok, I realize my post has become a bit of a ramble, hope it makes sense to someone! Cheers, Ally On Sep 13, 10:35 am, Matthias Nothhaft <matthias.nothh...@googlemail.com> wrote: > Hi, > > I also think it's a good idea to put the admin generator into a > separate bundle as everything is a bundle (I like that phrase). > > So.. to me the question is how should the concept be changed for > Symfony2? > > IMHO it is not necessary to have a generator.yml and auto generated > files in the cache. I would prefer something like that: > > - create a command that only generates the module (controller, > templates) in a given bundle > - inherit the controller from a special base class that provides the > default implementation > - forms can completely be configured in the form class and by ways the > validation component already provides > - for the list I think we should now introduce a real data grid > - for things like "object browser" and other more advanced "widgets" I > think all can simply be provided by appropriate form fields > - somehow there should probably be some magic to map the db schema of > a model to the form fields > > What do you think? > > regards, > Matthias -- 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 developers" group. To post to this group, send email to symfony-devs@googlegroups.com To unsubscribe from this group, send email to symfony-devs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
