On 19.07.2010, at 18:36, Lukas Kahwe Smith wrote: > > On 19.07.2010, at 18:25, Daniel Lohse wrote: > >> These two things (form system and grid component) should cover more than 90% >> of the current admin generator's feature set (and more, see the JavaScript >> part) and don't produce the same generated code that exists over and over >> again in the cache. :) > > > sounds good. > > what i would also like is to ensure that i can still naturally evolve the > solution to a totally customized solution in case the client requirements > slowly force me in that direction. so +1 for not generating controller > classes outside of the cache, but i still want to be able to "materialize" > things to be able to add custom logic.
The class-based approach should take care of that as you can sub-class it. But it's not like the current solution where half the code of the model generator class is about code generation and not about logic. ;-) > > regards, > Lukas Kahwe Smith > [email protected] > > > > -- > 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 [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-devs?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 developers" 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-devs?hl=en
