2011/1/25 Henrik Bjornskov <[email protected]>: > I personally do not think that most bundles will be small applications. I > think that most bundles will provide some form of aid in development like > MenuBundle, GravatarBundle, FrameworkExtraBundle, SecurityExtraBundle and > the list goes on. In my experience most applications are very specific about > what they do and how they do it.
So it seems that we need a clearer separation here: a) Bundles are Symfony2-specific, components not -------------------------------------------------------------------------- Bundles should only contain code that is dependent on the "Symfony2 framework". Everything else belongs to the "Symfony2 components library", i.e., the Component and Extension namespace. This part can be reused outside of the Symfony2 framework and documented separately. Bundles are designed to be used in Symfony2 alone 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. Thoughts? Bernhard -- Software Architect & Engineer Blog: http://webmozarts.com Twitter: http://twitter.com/webmozart -- 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
