> > 1. A readonly widget (for displaying non-editable values) > > What's the point of that? Is that not the same as echoing the value in > your template? >
For Symfony 1.4 I have developed some ReadOnly widgets, but with an extra functionality. I include the option "credential", in which, so only if the user has the credentials can modify the field, if he don't, it will be a ReadOnly field. For me it's useful when different people interact with the same form, I don't know if for others it might by useful or not. And there is something about the feature that Daniel talk? >the ability to break a form into multiple pages/parts (checkout process in a >shop, an upload process of an asset that requires multiple steps) Thanks for all On Oct 7, 10:25 am, Bernhard Schussek <[email protected]> wrote: > Hi everyone, > > First of all, sorry for the long silence. > > Second of all, thank you all for the feedback. Fabien is right, we > need people to test the Form framework thoroughly and provide > feedback. > > I will comment on some of the above-mentioned points: > > > 1. A readonly widget (for displaying non-editable values) > > What's the point of that? Is that not the same as echoing the value in > your template? > > > Embedded forms with dynamic "add new" and "remove" which don't > > require loads of manual boiler plate code to get working. > > This does already exists and is called CollectionField. It enables you > to dynamically enter collections of values (like arrays, Doctrine > collections etc.) - these values can of course be composite values > like arrays, objects etc. > > CollectionField is also designed to be supported by JS, though there > currently is no example of that AFAIK. > > > 2. the ability to keep an already uploaded file even if some other > > validators fail (this is tricky and always requires loads of code even if > > there are plugins for that) > > This is planned and I already developed a prototype for that. > > > Dynamic, dynamic, dynamic. Take the drop-down list with the label "How > > did you hear about us?", with options "Internet", "Radio", "Other". If > other is selected, a text input is made visible -- and should be > validated - but only when "Other" is selected. Currently doable? Yes. > Straightforward? No. > > There also exists a prototype for that. The question is how much JS we > will want to provide with Symfony2. > > > Changing the value of a field after a bind. > > Why? This violates the workflow of the field. > > > Extensibility. Extending sfFormField, for instance, is almost > > impossible because the name of the class is hard coded on sfForm and > sfFormWidgetSchema. > > Solved. > > > Currently there's no easy way to do a $form->getObject() on an > > embedded form > > Solved. > > > Only shortcoming i have is i cant attach constraints to to fields directly > > from the form it self. > > Possible by adding a constraint on the getData() method of the field. > Look at the validation.xml bundled with the Form component for an > example. > > Bernhard -- 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
