> > b) Bundles can contain anything useful for developing with Symfony2 > > ---------------------------------------------------------------------------------------------------- > In this case, bundles are designed to be reused outside of Symfony2 > (and are documented and advertised to be used there), although some > parts of the bundles are Symfony2 specific (the Bundle class, for > example). The question is what the real difference between components > and bundles is now, because user-provided bundles (e.g. MenuBundle) > would basically be the same as a core component + resources and DI > configuration. > This is what i think, and this is also what people are already doing today and can be seen in MenuBundle, GravatarBundle etc. Why would there be a reason to only have bundle contain specific code for Symfony2 integration? This would lead to a massive amount of Namespaces and Libraries for a project if it used one or more 3rd party bundles as the bundle would only have DependencyInjection config and extension and the bundle class.
The overhead of classes to include in a project would also be reduced by this as the core is lighter and slimmer by having bundles include classes. The proposed Extension/Tein is the same as a lightweight bundle (a bundle with no config.xml / dependency injection extension) -- 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
