Jamie Learmonth wrote: > Hi, > > What really bothers me is that, from my point of vue, it should be a > plugin (as main external library like Propel and Doctrine), and not > comes from the symfony core, because in the current situation, > nobody can disable this library (that is a bad thing) without > changing the core of symfony (that is never a good idea). > > > I agree that it does go against the philosophy which was adopted by > symfony since 1.1 to decouple components from the framework, but with > 1.4 around the corner this may be prove to be a really big change at > this stage. > > But, if the core team agree with the argument I am sure they can pull > something out the bag.
I started the Swift Mailer integration as a core plugin but changed my mind due to the current constraints of the architecture of symfony 1.X. Hopefully, with the new architecture of Symfony 2, it will be easier to make an independent plugin, but for now, I think this is much safer to keep it the way it is. Fabien > > Jamie > > > -- > > 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=. -- 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=.
