I would probably agree with chtito here, however i would like this feature if it was implemented as follows:
Lets say myGenerator extends sfDoctrineGenerator extends sfGenerator, then i think that the way it should work, is that if i have a theme, 'default', it looks first for templates for the default theme of myGenerator, then if it cannot find them here it looks for those in sfDoctrineGenerator, then in sfGenerator. So, in summary, only templates within the the same theme for classes in the inheritance chain of the generator class are loaded. Templates in different themes, are not loaded, making a theme's templates exclusive to that theme, but retaining the ability to override that theme's templates by creating a class that inherits from the appropriate generator! On 9 Feb 2007, at 15:30, chtito wrote: > > <http://www.symfony-project.com/trac/changeset/3325> > Was this changeset really tested? Has anyone successfully used it? As > far as i can tell, this changeset doesn't work. Besides, i think that > its purpose is doubtful: what if i wanted to have a much simpler theme > with less files? I consider this changeset both unpractical and bugged > and i'd rather have it reverted. > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
