If you want to make some changes to the generated classes, you should consider listening to the post command event of the build task, and then modify the base classes. For example, I do this to change the default options for some validators.
In your case, you can exchange all instances of sfWidgetFormInputText with myWidgetFormInputText which in turn extends sfWidgetFormInputText. This way, you get your proposed change without altering any classes in the core. Kind regards, Johannes On 1 Sep., 00:43, Tom Boutell <[email protected]> wrote: > I wouldn't bring up things like this if I didn't want to use Symfony > 1.4 anymore. (: > > The suggestion I made is backwards compatible. > > Fixing the build task to make it easier to specify alternate form > generators for Doctrine, and perhaps pulling the default choices from > factories.yml, would also be backwards compatible. > > I'm happy with 1.4 and getting tremendous amounts of work done with > it, but figured it couldn't hurt to make a suggestion, especially one > that does not break other people's code. > > I agree that a 1.5 release doesn't make a lot of sense. > > On Tue, Aug 31, 2010 at 6:17 PM, Matthias Nothhaft > > > > <[email protected]> wrote: > > It does not make sense to work on an sf 1.5 version - for the reasons > > you mentioned: BC break is a no go. IMHO all "problems" can be solved > > by creating an appropriate plugin. > > > I really don't understand this 1.5 discussion. 1.4 is stable and has 3 > > years support and after a few months it already seems nobody wants to > > use it anymore.. Doctrine 1.2 also is stable so.. I would expect some > > nice projects on top of sf 1.4, for example a CMF (would make sense > > from business perspective) but instead people complain about sf 1.4 > > (again: it is stable) and wait for Symfony2 (will not be stable this > > year).. so.. I really don't get it.. > > > regards, > > Matthias > > > On 30 Aug., 17:38, Lukas Kahwe Smith <[email protected]> wrote: > >> On 30.08.2010, at 09:29, Stéphane wrote: > > >> > Any 1.5 so ? :-) > > >> > Shall we fork this ? > > >> > Any PoC on DI on forms on SF 1.4 ? > >> > What would it take to do so ? > > >> if there are _several_ worthwhile improvements on the table on top of 1.4, > >> i think we should consider a 1.5. in this case it wouldnt make sense > >> however to introduce the SF2 Di or form classes. for one they are 5.3 only > >> .. but more importantly it only makes sense to do a 1.5 if there are close > >> to zero BC breaks and essentially just feature additions. if there are a > >> ton of BC breaks in 1.5, then you might as well make the jump to symfony2. > > >> regards, > >> Lukas Kahwe Smith > >> [email protected] > > > -- > > 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 > > -- > Tom Boutell > P'unk Avenue215 755 1330begin_of_the_skype_highlighting 215 755 > 1330 end_of_the_skype_highlighting > 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
