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.
I can also see some bundles providing basic controllers that does just one thing like ForumBundle (Its a Forum yes, but an application no) and another example of this MessageBundle. They both have the same thing in common that they need the developer to do one or more things. Mainly templating work but also some degree of integrating them into the application on some level. As you said the Core bundles are a little bit different because they mainly clue things together but this is only in a one or more config files or in a DependencyInjection extension. This can easily be taken out of a bundle or simply ignored. At the last meeting the bundle refactoring was "approved" so they now must follow the PSR-0 naming convention. This makes them even more reusable outside of Symfony2 and also advertise to be done so. I can see a library contain a vendor namespace with it libraries and then maybe a bundle namespace with a bundle that makes the library integrateable in Symfony2 by a DependencyInjection 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
