Expose plugins like a service. def plug(): return plugin()
/init/default/plugin/comments/view/hi/ or /init/plugin/comments/view/hi/ -Thadeus On Tue, Nov 3, 2009 at 8:37 PM, Thadeus Burgess <thade...@thadeusb.com>wrote: > Here... change the routing for plugins. This allows us to actually have the > plugins in a subfolder. > > URL(r=request, a='plugin', c='comments', f='view', args=['hi"], vars={}) > > -Thadeus > > > > > > On Fri, Oct 30, 2009 at 7:58 AM, Yarko Tymciurak < > resultsinsoftw...@gmail.com> wrote: > >> >> >> On Fri, Oct 30, 2009 at 5:35 AM, Jon Romero <darks...@gmail.com> wrote: >> >>> >>> how about this: >>> The (main) problem (as I see it) with Massimo's approach is polluting >>> directories with plugin files (and maybe making it more difficult to >>> add/remove plugins). >>> >> >> That is just the most obvious issue with that approach... >> >> >>> Besides that, I think it is a very easy way to add plugin capabilities >>> to web2py (without changing much of its architecture). >>> >> >> "...without changing much of [web2pys] architecture...." is irrelevant. >> In fact, the only "important" thing is maintaining backward compatibility >> (e.g. not changing web2py behavioraly, or at existing interfaces available >> to applications). If any existing web2py coupliing (for example) where to >> be cleaned up because of what was discovered to be difficult from defining a >> reasonable plugin system, that would be a GOOD thing! >> >> I think the current way is insufficient (see my recent post for one >> example of why I think we need more than is currently there). >> >> >>> >>> So, what if there is a central plugin_config.py that defines what each >>> plugin does (documentation), version and files (models, controllers >>> EVEN static files) and url for updates? >>> >>> I imagine being able to do something like that: >>> $sudo web2plug install CMS >>> downloading 3 files >>> .... >>> .... >>> Done >>> >> >> Yeah - I think some way of "broadcasting" plugin capability is needed, and >> some way of registering that too... I think we need _more_ than that (i.e. >> "not 'Done'!"), but I think that is a piece. >> >>> >>> and then info is added in the plugin_config.py (so it's easy to remove >>> it - manually or automagically). >>> >> >> There may be a better way to do this, but the concept is in the right >> space - we need to think through this more I think. >> >> >>> Also, the admin page can provide an update interface for plugins JUST >>> by reading a file (also, no speed problems - we are reading a file at >>> the start). >>> Ideas? >>> >> >> You could prototype this to show how it would work (although I think a >> little more discussion is still in order, first...). >> >> >>> >>> >>> >> >> >> >> > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---