On Oct 22, 5:54 am, "Grégoire Hubert" <[EMAIL PROTECTED]> wrote: > By experience I know thosetemplate«markupped» languages have > limitations you sometimes have to bypass. In the end you have > templates with an ugly mix of templating language and real scripting > language. >
You've explained a situation where the separation of display logic from application logic has been broken, and made a strong case for the need for a templating engine that at least makes doing so hard to do. In the model I propose: - 1) whatever you needed to do couldn't be done in a helper or in the controller (I'm not sure I can think of a use-case wfor this, but assume it was necessary ....) - 2) you would have to - in the controller or config - turn on the ability to use PHP in the template. Hopefully jr. developers with a tendency to do that would not make it a habbit. At the very least, it would be a good clue to look for something during the code review. - 3) Since the templating "language" looks pretty much like HTML extensions, the <?php ?> would be somewhat self-documenting - at least to the extent it would stick out like a sore thumb in a text editor, and probably break XML validity, though it would be invisible to a browser. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
