On 13.09.2010, at 11:35, Matthias Nothhaft 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?
i havent really hacked much in admin generator modules internals, but what i wish for is that the transition from going to generated to custom coded should feel natural. aka once you outlive whats possible with the generator it should be painless to just custom code. maybe i just dont know the current generator well enough, but this was always a bit of a concern for me. regards, Lukas Kahwe Smith m...@pooteeweet.org -- 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
