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). Besides that, I think it is a very easy way to add plugin capabilities to web2py (without changing much of its architecture).
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 and then info is added in the plugin_config.py (so it's easy to remove it - manually or automagically). 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 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 -~----------~----~----~----~------~----~------~--~---
