On 13.09.2010, at 17:16, Tom Boutell wrote: > Philosophically I think this is a great solution. I hope the > performance issues can be finessed. My understanding is that templates > are a lot faster in 2.0...
i guess one key thing is the enable caching here (which certain widgets might need to partially disable). of course there is always dynamic stuff like prefill values and error messages that need to be added to the template, which in order to be unobstrusive/accessability friendly cannot just be send to the client separately. all solvable of course but of course adds additional challenges especially if the solution should be template engine agnostic. 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
