Quoting the intro of the plugins section of the manual, "CakePHP allows you to set up a combination of controllers, models, and views and release them as a packaged application plugin that others can use in their CakePHP applications...Package it as a CakePHP plugin so you can pop it into other applications."
This pretty much sums up the original intent of a plugin as a portable, distributed, mini app. As such, Plugins would have no knowledge of the main application, so they can be easy added to an existing application without requiring any extra configuration or the addition of other classes. Essentially, what you are talking about would be creating dependencies that were not intended. Correct me if I am wrong, but it seems some are using plugins to organize parts of a larger application. To me, you are on a slippery slope here to basically negating the whole benefit of a plugin and just making it more work on yourself. Using the config/bootstrap.php to organize your MVC requires a lot less code and should yield the same benefits. That said, there are some changes in the works that may allow this functionality. So time will tell, but at least you know why it works the way it does right now. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" 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/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
