Yah thats right. Having Symfony\Tiein would lead to complex discussions of wheather a Doctrine class needs to be in the Bundle or the Tiein and details about configuration and such. Bundles would then be essentially just the DependencyInjection namespace + some resource files. As a downside this would be yet another concept. Having everything Doctrine related in a Doctrine Bundle has its benefits, if we can guarantee to people that they can use it in their own projects without problems.
Just shipping bundles and components however also means that non-symfony framework users have the avoid the bundle concept and the Bundle + DependencyInjenction + Resources/ files. But personally I would rather put more complexity to non Symfony framework users than the other way around. I think its much easier if Security DBAL and Doctrine Form components would all be in the Doctrine Bundle. That way if you dont use the Doctrine Bundle, but the MongoDB bundle you can have your own acl provider and all the implementations aswell as form fields. The responsibilities all feel better than the way it is currently. This will prevent the core getting bigger and bigger all the time only because Doctrine gets bigger. greetings, Benjamin On Tue, 25 Jan 2011 07:19:10 -0800 (PST), Henrik Bjornskov <[email protected]> wrote: > How do we then decide what goes where? > > The problem with this is the same as before. It will still partly be in > core. Lets say we move DBAL Security to Symfony\Tein\Security\DBAL where > should the init command now be? Should that be a part of the Tein package? > > Right now FrameworkBundle init:acl borrows the dbal.connection > configuration > from DoctrineBundle config files. That also says something about where it > should be. > > Another problem is when do we stop adding stuff to Tein? If tein is > created > we have to move all Doctrine ORM/ODM/Couch/PHPCR/Propel/Other into tein. > How > do we decide who to include and who to exclude? > > The bundles people using a Component can still use bundles as they where a > little library and remove all the Symfony2 specific code and that means > they > dont really have to know what a bundle is. We can just start to > "advertise" > a bundle to be downloaded and used outside Symfony2 especially now we use > the PSR-0 naming conventions for theese aswell. -- 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
