This is a recurrent theme on this list and one I care the most. It is also a complicated issue because different people define plugins in different ways and because it is a matter of writing specs more than a technical issues. Anyway...
In web2py we do not have the concept of projects. We have the site (one web2py folder) and multiple applications for a site. An application can be a plug-in in the sense described in http://www.web2py.com/examples/static/plugin_t2.pdf I think we should also plug-ins in the sense of "things" that plug into an application. While an application is a zipped file that unzips under a new application folder, a plugin would be a zipped file that unzips ONLY under an existing application folder IF it does not override any existing file UNLESS the existing files constitute a previous version of the same plug-in. A plug-in could contain modules/plugin_xxx/* models/plugin_xxx.py controllers/plugin_xxx.py views/plugin_xxx/*.html static/plugin_xxx/* and it would also contain a metadata file of some kind plugins/plugin_xxx.meta? We can imaging more sophisticated admin, layout.html, etc. that know how to interpret the metadata file. We need to come out with specs for writing these metadata files. What should be in there? Once this is solved everything else can be coded in one day. Massimo On May 3, 6:47 am, Kless <[email protected]> wrote: > Is there any plugin system for reuse/share applications in another > projects? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" 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 -~----------~----~----~----~------~----~------~--~---
