Here is what I would want. Download a plugin...
Install it on my app... Define default variables for the plugin to use (things like the database, etc.. etc..) Expose it in my controllers, passing it optional parameters... Be happy. I volunteer to create and host web2py-plugincentral.com (or if anybody has a better name) to manage and browse plugins. In fact, I have already started working on it. Do we still need a way to package plugins? If so I could work on that as well while I am at it. Plugin installation should work just like app installation, either browse and upload, or specify external location it could be downloaded from. Personally, I have been wracking my brain for the last 30 minutes to try to find something that LOAD would not provide, and not seeing much wrong with it. It would be nice to be able to access a plugins global vars, but see no reason in this. Are plugins also able to take advantage of services? If I have a plugin that returned json or html depending on what is returned from ajax. I think plugins should be responsible for refreshing themselves, form trapping is nice, but it limits what could be done, easy, but limiting. -Thadeus On Wed, Oct 21, 2009 at 1:42 PM, mdipierro <[email protected]> wrote: > ose of a plugin, as I intend it, is not to replace the concept > of python modules (i.e. pieces of codes that you import once and are > available everywhere), it is not to create > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
