As far as the plugin thing, you can certainly try, but high-level components like that aren't always re-useable. Certain things like forums are definitely more trouble than they're worth to build from scratch over 90% of the time, but with other things, the stuff that's specific to the application it is being plugged into can almost outweigh the plugin itself.
If you try to compensate by writing your plugin to be flexible enough for every possible scenario, you end up with an unwieldy beast that's more complex than most of the applications you're plugging it into. As far as JavaScript and vendors, there's really only one use for that, and Cake already has built-in support for it. If you put any JavaScript files in /vendors/js (the vendors folder in the root, not in app), or any CSS files in /vendors/css, you can load them the same as if they were in webroot/js or webroot/css. Well, almost the same, as any files loaded from here are PHP-enabled, meaning you can embed PHP that will be evaluated before the file is sent to the browser. So, why only the root vendors folder? Because if you're running multiple apps off of a single Cake core, all those apps can share the same JavaScript files. Imagine being able to update Prototype and script.aculo.us once for all your applications. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
