I think the template approach is great for the more complex widgets/ fields. But my experience is that most fields consist of single HTML elements (input, textarea, etc.), and I don't think that you need a template for them. So maybe, a hybrid solution would be ideal.
Johannes On Sep 15, 2:59 pm, Fabien Potencier <fabien.potenc...@symfony- project.com> wrote: > On 9/15/10 2:47 PM, Dennis Benkert wrote: > > > As a reminder, another possible approach is the way Agavi does it: you > > just define your html by hand (it could be optioanlly rendered by those > > subtemplates and cached) and then validation/auto-fill is added by > > transforming the output of the page with xslt. The advantage in this > > case is that you only call the slow code when the user actually submits > > a form and it doesn't validate. All other requests are just hitting the > > template and rendering straight. > > > But this would also include that your html code has to be 100% valid all > > the time, doesn't it? In nearly every Agavi project we did we had hard > > times getting FPF (Form Population Filter) pleased because of html > > validation issues. Or aren't you talking about the FPF mechanism? > > That is what we had in symfony 1... with all the problems. And this is a > totally different approach as you loose all the benefits of the form > framework. > > Fabien -- 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
