It would still be index.renderer.phtml (the same as index.renderer.html), I'm only for the extension change, not the renderer part removal, as phtml semantically would make sense (expected html and/or php code). -- Aurelijus Valeiša
On Wed, Jan 19, 2011 at 7:04 PM, Christophe COEVOET <[email protected]> wrote: > Le 19/01/2011 10:49, [email protected] a écrit : > > I think it's not only about IDE's. Let's say template engine is php, then >> in my understanding it would be index.php.html, which wouldn't be a bit >> confusing semantically. That's why we use extensions - to define what file >> type it is. >> >> I would vote for .phtml extension. It would make a lot of sense as it will >> be compatible with html and php templates, and also twig. What is more, IDEs >> won't have a problem with that. >> > And how will you make the difference between a Twig and a PHP template (or > another engine) to choose the good engine ? > > Thus, it does not solve the problem for other format: xml, json... > > -- > Christophe | Stof > > -- > 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]<symfony-devs%[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
