On 22.10.2010 11:31, Lukas Kahwe Smith wrote:
>>> Please, don't do that. We had that in symfony1 and let's not do the same
>>> errors again.
>>
>> I think it may be ok to have a one-liner solution as long as it's still
>> very easy to expand it to a full fledged hand-crafted form definition
>> (which is already possible..). The problem I think occurs when you focus
>> on the one liner first, and then get stuck trying to implement
>> flexibility later on.
>>
>> However I don't really mind doing the form tag and submit by hand, so
>> I'll drop the issue if you really think it's a bad idea.
>
>
> i think he was referring to my proposal of rendering an entire form with a
> single instruction, i dont think he was speaking out against having an
> instruction to render just the <form> tag ..
Yeah ok, but once you have the thing to output the form tag, and the
thing to output a submit button, then it becomes fairly easy to add a
new form.twig block that would render the top level form, so that when
you do {{ form|render }} it actually outputs a full form.
Cheers
--
Jordi Boggiano
@seldaek :: http://seld.be/
--
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
