I don't think we should delete sfMixer quite yet. sfPropelPlugin for 1.3 should be able to be a drop-in replacement for symfony 1.1. Deleing sfMixer will prevent any 1.1 application from using sfMixer as well.
But, for sf1.2, I think sfMixer can go in favor of the event dispatcher. Carl On Aug 24, 6:56 am, Kris Wallsmith <[EMAIL PROTECTED]> wrote: > Yes, the sfMixer class has been removed from sfPropelPlugin 1.3 > because it is no longer used there. We can release a sfMixerPlugin if > you're using this class in your own code. > > Kris > > On Aug 24, 2008, at 5:46 AM, Igor <[EMAIL PROTECTED]> wrote: > > > > > You are delete sfMixer behavior :(? Why? > > > On Aug 23, 11:34 pm, Kris Wallsmith <[EMAIL PROTECTED]> wrote: > >> Hi plugin devs, > > >> I just committed a rewrite of the sfPropelPlugin behaviors system to > >> the plugin's 1.3 branch. This update should maintain BC with all your > >> sfMixer-style behaviors, but please run your tests to confirm. If you > >> see unexpected behavior, post a ticket for me, Kris.Wallsmith. > > >> Kris --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
