In all of the third party bundles I've looked at, all forms for the bundle seem to go in SomeVendor\Bundle\BundleName\Form. That's how I've been organizing my own forms as well since it makes them easy to find and the namespace makes sense.
Personally, I tend to organize classes based on their function. For example, I have multiple services in one of my bundles that I have in the SomeVendor\Bundle\BundleName\Utils namespace since they're all utilities. Encoders go in SomeVendor\Bundle\BundleName\Security\Encoder. And so on. If you find that your bundle is getting too big or has mixed functionality (e.g., a gallery and a blog), then that's probably a good indication that you should break the code up into multiple bundles. There isn't anything that says you *have* to do that but it makes your code more reusable and easier to organize. -- 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 users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en
