Massimo - For the purpose of this kind of discussion, it is useful to talk about "components" (plugin is sort of a concept about how you use / deploy components).
So in general, a solution (application) is made of components. To be reusable (where possible, desireable) components must be encapsulatesd, and have an interface to interact thru. What you have done so far is say "one component may span all layers (e.g. 3 - presentation aka view; persistence aka model; business & engineering logic aka controllers)" - so that definition has implications on how the interface needs to look to interface w/ gluon... ... this component aspect is so fundamental that I think discussions about "web2py might have to change implementation" are well to be put off, at most replaced by no more than discussions of backward compatibility (that, after all, is what is important - refactoring gluon core, watching performance is just "work"). The bigger, longer term benefits tell me this discussion should stay a bit broader, higher level for a while. - Yarko On 10/1/09, mdipierro <[email protected]> wrote: > > 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 -~----------~----~----~----~------~----~------~--~---
