> 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.
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. My goal really was to make an application shell comprised of "plugins" or whatever you want to call them, and just plugin which ever plugins I needed for the client, then supplement with whatever client specific glue or app code was needed. Since plugins are not meant to be used this way, and we should be using the bootstrap.php approach, I guess I need to understand that approach better. What does it entail? Can we still place our (let's call it) "addon" in a single folder and point cake in such a way as to find the addon's controllers, models, views, helpers, components, etc? Can the addon's controllers access the main app's models? What about images and stuff normally stored in webroot? Can the addon- specific files be placed in the addon folder, and is there a way to enable the user's browser to be able to download the addon specific images? Guess I'm short on understanding how to organize code for "addons" which can access the main app, and the main app can access it's code, yet still keep everything related to the "addon" in a single folder. I supposed it can be done somehow with routes, but not sure that is the cleanest way. Hopefully gwoo or someone else can explain (in a little more detail than gwoo's post above) how this might be done? I haven't seen anything related to this on this forum or in the manual, so it might be of benefit to people. BTW - I have lots of trust in the approaches chosen by the emminent cake developers until now in so many areas, so am not at all criticizing. Just trying to wrap my head around something I have not seen explained in the year or so I've been following this discussion group. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
