We should create a web2py plugin package manager. Have a central database of plugins (and versions), and in the admin interface you can select a plugin that you want, and web2py will go download it and put it with the app (and alternatively keep it up to date through the admin interface)
Also with dependency checking, so if a plugin requires another plugin, web2py will download both plugins. Plugins could be version controlled, with mercurial, so if you need to make edits to a plugin, you can still update it, but not lose your changes. Also, say I have a blog, using your comments plugin, how would I specify in the database structure that a particular comment belongs to that post? Perhaps one of the vars that gets passed to the plugin could be something such as uuid? Bringing me to the question, the LOAD(vars=dict()) are those available to the controller of the plugin in global namespace? and args gets passed to the URL()? If so that would work. -Thadeus On Wed, Oct 21, 2009 at 11:44 AM, Renato-ES-Brazil <caliari.ren...@gmail.com > wrote: > > I think versioning is very important. > > On 21 out, 14:25, Yarko Tymciurak <resultsinsoftw...@gmail.com> wrote: > > On Wed, Oct 21, 2009 at 11:16 AM, mr.freeze <nat...@freezable.com> > wrote: > > > > > I like how the plugin system is shaping up but have one question about > > > the folder structure. It seems more manageable to structure it like > > > this: > > > > > applications > > > -- my app > > > ---- models > > > ---- views > > > ---- controllers > > > ---- plugins > > > ------ myplugin > > > -------- models > > > -------- views > > > -------- controllers > > > > > This way a plugin would basically be a sub-app, making it easier to > > > install/uninstall/upgrade and could also have multiple models/views/ > > > controllers. I remember some discussion about it but can't remember > > > what the reasons against it were. > > > > <sarcasm flag UP> > > ...yes, with the added benefit that you get to make copies and copies of > > plugins into every applications that needs it, woohooo!... > > </sarcasm> > > > > Seriously, folks - think about plugins in other systems. > > Plugins need to be that - logically, I expect them to be per web2py > > installation (not as a component within an application); > > Logically, I also _might_ like to see them versionsed, so that pluginA > has a > > DEFAULT version which links to a specific version (without talking about > the > > mechanism for that "linking"). > > > > > > > > > On Oct 21, 10:18 am, mdipierro <mdipie...@cs.depaul.edu> wrote: > > > > The new web2py in trunk (1.68.2) also contains an improved > > > > experimental solution for plugins. > > > > Here is a new video about it > > > > > >http://www.vimeo.com/7182692 > > > > > > It includes suggestions from various people but I am sure it still > > > > needs a lot of work. Anyway, give it a try and let us know what else > > > > would you expect from a plugin system. > > > > > > The interface for uploading/downloading plugins is missing, among > > > > other things. > > > > > > Massimo > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
