I'm having a hard time understanding how the new form system really *works*. I understand the examples from the book and have no problem customizing the form templates. But how the different classes relate to each other, what class creates what effect, I have no idea. It would be cool to have some kind of explanation of the "Form life cycle" in the documentation. Some basic reference that goes beyond the question "how to build a form get get a value object from it" but is more concise than reading the code of the form classes.
Here are some questions that may form the basis for such a document (or just document my cluelessness) - What happens when a form builder is invoked? - How is it invoked? - What's the difference between the user defined form type (inheriting from AbstractType) and the Form class? - What's the purpose of FormTypeInterface::getParent? Why not use Reflection and checking for inheritance? - How are the parent-child-relationships of FormType used? - What is FormTypeExtensionInterface (and the abstract class) for? - How are the different parameters for the Form constructor collected? - What happens when "bind" is invoked? In the end, the values given to "bind" are set in the data object, but what happens from the "bind" call until the setYYY mtehod of the data object is called? - What events occur in the form lifecycle and how can I hook into these events? - How does the FormView class work? How does it assemble the view for a form? -- 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 users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en
