Hi Steve! Yes, as Vincent eluded to, this was a purposeful design decision. Unlike symfony1, the fields in Symfony2 have just one job: to move data back and forth between the domain object and what the user is seeing/submitting. So, the fields are 100% agnostic of actually being rendered. The advantage is that the markup for a field now lives inside a template instead of inside PHP classes as it did in symfony1.
So yes, it's a different mindset, but it should make your life easier in most cases. I understand that this means that you can't render the whole form with one line if you need custom attributes, but rendering with just one line is really meant for prototyping anyways. I hope that helps clarify! Ryan Weaver US Office Head & Trainer - KnpLabs - Nashville, TN http://www.knplabs.com <http://www.knplabs.com/en> http://www.thatsquality.com Twitter: @weaverryan On Sat, May 7, 2011 at 12:23 PM, Vincent Lechemin < [email protected]> wrote: > it's possible but while rendering in the view which is more logical > > -- > Vincent Lechemin > > -- > 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 > -- 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
