Hi, I'm following discussions about that for a while now, and i must admit i totally agree with Benjamin (Eberlei), and Henrik (but in a moderate way). And even more when i read Jordi's arguments.
However, i don't agree about exception templates and form templates, or any template, being part of the TwigBundle. My understanding of the bundles is that TwigBundle, for instance, is meant to add Twig support to a Sf2 project, and that's it, no more, no less. IMO, each Bundle should ship templates for engines they decided to support. Indeed, that would bring a lot of files which would never be used, but i think that will always be the case, no matter the way you choose to go with. I admit i'm a bit frustrated about the decision to "accept" some external dependencies into the core because it's a closed door for some "not well known" tiers libraries/frameworks (home made i.e) which could never be integrated as good as Doctrine is for instance (not sure about the english of this sentence :p). But it's also an (dangerous) open door for the future : "Hum, we did before, why not doing it now ?" and that could lead to a "dirty" and someway "tight" core with time. And i'm even more concerned since i choosed to use Symfony 2 because i was so glad and surprised to see the direction it took about flexibility and reusability. Cya, Benjamin -- Benjamin Dulau - anonymation CEO anonymation.com | code.anonymation.com [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
