On point 1, I think it would be nice if we could configure a list of form and filter classes that we don’t want generated.
There is really no need to generate form classes for the m2m relation tables, the Versionable tables… I also have this ticket <http://trac.symfony-project.org/ticket/5014> pending for 1.3 to allow for custom generator classes to be used by the build-forms and build-filters tasks so that we can customize the generation process. From: [email protected] [mailto:[email protected]] On Behalf Of Thomas Rabaix Sent: Thursday, March 05, 2009 7:55 AM To: [email protected] Subject: [symfony-devs] open discussion on sfForm Hello, Point 1 : I think symfony generates to many classes : Form and Filter. I will prefer to generates this class only when required, having less class cannot be bad. Point 2 : Next, It is bad to generate project wide form/filter classes as depends on the application validation maybe changes : admin can have more control over the form. So the generator have to generate 3 files * BaseYourModelForm.class.php : file with the basic widget definition as now * SharedYourModelForm.class.php : the dev can globally overwrite definition from BaseYourModelForm (acts like the current YourModelForm) * YourModelForm : inside the application lib Point 3 : Model Form should have a method to define which fields we want to use. This will avoid bugs when adding new field into the model, as the base form will use them on update. -- Thomas Rabaix http://rabaix.net --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
