Shouldn't these have Base classes so we can override at project level and have that automatically respected by doctrine and propel forms?
That is: sfWidgetFormInputText -> BasesfWidgetFormInputText, with sfWidgetFormInputText an empty wrapper extending that Then if you define sfWidgetFormInputText at the project level, also subclassing the Base class but also adding functionality, that wins. Just like BaseForm. Makes it drastically easier to enhance the widgets especially those that don't have any outer wrapper element to hang your CSS and JS on (time and date especially). Also you can choose to extend some other subclass that's in a plugin, so it's easy to reuse other people's enhancements to the stock widgets. The base classes can autoload, so no need for crazy require statements. Should be a backwards compatible change. This compares favorably with the complexity of configuring the doctrine factories to use different widgets, plus that wouldn't help with any instances not created by Doctrine. -- Tom Boutell P'unk Avenue 215 755 1330 punkave.com window.punkave.com -- 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
