thinking aloud... It seems to me that a plugin is not necessarily a self contained object and it does not have less rights than an application.
Any subset of an application can be a plugin. An entire application can be a plugin of another application. A plugin of one app should be installable somwhere esle as an its own application. Consider the plugin_comments. I could install it on my machine and you could embed the component (the one line JS) without you installing any code. For me its is an app, for you it a javascript line. I imagine building collaborative distributed applications with plugins, not just you downloading a folder and running it. On Oct 1, 12:42 pm, Jon Romero <[email protected]> wrote: > I think this is awesome and it was missing from web2py. > > The only thing I found strange, is that you have to place the files > inside your application in multiple places. How about creating a > plugin directory (see Rails "vendor/plugins") where you could just > place the whole plugin structure there (like an autonomous > application)? I know this might make the code more complex but it > separates plugins from your application (also easier to try many > plugins without 'polluting your app' and it's easier to upgrade). --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" 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/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
