No, thats up to JavaScript, symfony shouldnt Be coupled to javascript. But you Need it for sure, we implemented this with 3 lines js in our own js Library. So no Problem for that.
The readonly Problem can be solved with an Event, simply add disabled=disabled to every Widget in the Event callback. All probs moorehouse listed are valid. I Want better Support for relations. Greetz Robert sent from Phone Am 28.09.2010 um 16:02 schrieb jaime <[email protected]>: > Also a widget for dependent choices: when you select one choice the > others change their values. > > Like this plugin > http://www.symfony-project.org/plugins/sfDoctrineChoiceChainPlugin > > On Sep 28, 9:48 am, jaime <[email protected]> wrote: >> +1 for Phil Moorhouse common problems. >> >> I developed in my own: >> - A read only widget for each kind (text, textarea, choice, >> checkbox..... ) >> - A widget for embedding forms in a dynamic way. >> >> Also I find that it's necessary a choice widget or autocomplete, that >> give us the possibility to add a record if not exist. Like this plugin >> works:http://test.ical.ly/2010/09/23/sfadminhijackplugin-%E2%80%93-how-a-hi...) >> >> For giving our customers a good experience about Symfony2 it's >> necessary to have better forms according to the problems many of us >> hve in Symfony1. >> >> On Sep 22, 9:26 am, Phil Moorhouse <[email protected]> wrote: >> >> >> >>> Hi - I noticed there's been a fair bit of discussion on the form >>> framework for Symfony2, and I was wondering if whoever does eventually >>> take over development was planning on requesting feedback from the >>> community on what they felt the issues / stumbling blocks / missing >>> features of the framework were in symfony 1.x? >> >>> I think it would be a good idea to at least talk about use-cases where >>> "average" symfony users (in which I include myself) have been >>> struggling so that we can look at avoiding them for Symfony2. >> >>> From following IRC, I'd say two of the most common problems are: >> >>> 1. A readonly widget (for displaying non-editable values) >> >>> 2. Embedded forms with dynamic "add new" and "remove" which don't >>> require loads of manual boiler plate code to get working. >> >>> I'm sure there are others as well. >> >>> Cheers, Phil > > -- > 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
