This was brought up before, but never revisited. Here is the post that summed it up for me:
"This is the first I've heard of this, although I can see the sense in gwoo's words. Plugins need to be independant, or they can't be easily distributable from app to app or developer to developer. So, I guess gwoo is right, I had intended to use plugins to organize parts of a larger application. Sounds like many others also thought this way." - keymaster I'm also working on a large project and ideally I'd like to organize the project based on package, where each package has it's own folder structure of model / view / controller. Gwoo has addressed this and said it can be done through the bootstrap.php, but never really specified how. This is what he wrote: "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. " I was wondering if there is any new information on this. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
