My input from building web applications (including a large, dynamic
one still in progress):
Stateful forms - so I can click 'New Product', open a popup and create
related records and 'save' them - all before the initial form is saved
(and they are discarded if the initial form is discarded). More of an
application pattern, but a use-case I run into a lot.
Dynamic rows/fields (a la 37 Signals, or Gmail contacts)
Showing/hiding/changing field type(s) depending on the current user's
permission. All too often I have a field ("Select which sales center
this relates to" for example) which some users can pick from, and
other users can't. It's easy enough to convert the field to a hidden
field, but actually it should be removed or restricted in a way that
cannot be tampered with. There are 3-4 solutions with the current
forms, none are what I'd describe as elegant.
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.
Daniel's two cases are also pain points for me, especially the file
upload issue.
Peter
--
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
