If I understand correctly, I think the best way to handle it is not to use widgets for the HTML and just use a form to validate the submitted value in your action.
Fabien Ian wrote: > So I have a form situation and I'm deciding the best way to approach > it. Basically I have a nested set (Doctrine) of product categories. > On this page, I have the ability to delete any category. I also have > 1 form option that goes along with each delete, a checkbox option to > also delete sub-categories (the nested set categories) if they exist. > > So this situation is basically the same small form over and over, > maybe 20+ times. My question is, is it worth it to create a whole > myCategoryDeleteForm() for this small instance? I would have to have X > instances of the same form on the page, and the post validation might > get hairy, especially with how you have to name forms, etc... > > This was easy with the old framework, but now that we have classes to > handle the forms, it may be a better idea to just use straight HTML in > these situations. Any thoughts? > > -- Fabien Potencier Sensio CEO - symfony lead developer sensiolabs.com | symfony-project.com | aide-de-camp.org Tél: +33 1 40 99 80 80 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
