Le 24/02/2011 10:05, Gerry a écrit :
Thank you for your answer Ryan.
I see how giving descriptive names to bundles, prefixed with the
vendor name is about the same in avoiding collisions, and when
specifying controllers in routes. However, in my opinion it is counter-
intuitive to define a PHP class FooVendor\BarPackage
\FooVendorBarPackageBundle or at least somewhat disappointing for a
next-gen PHP framework, which in every other regard is benefiting from
namespaces.
Also in this (admittedly early) stage, I'm under the impression that
this practice is not well adopted in the bunch of public bundles being
developed already. I've seen AdminBundles, BlogBundles, TwitterBundles
etc. Given that Bundles are just as well used for the plugin type of
functionality we loved in sf1, it bothers me a little.
Many bundles were created before these best practices were written.
Thus one issue when searching a bundle now is being sure it has been
updated to follow the changes of the framework. Some of them are totally
outdated
--
Christophe | Stof
--
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
