@mr.freeze Here are some quotations from what Massimo has previously said (on 1 Oct) .... HTH ---------
- having a plugin folder means web2py would have to look for models in multiple places. It could be mimicked in admin (the developers should not see the plugin_* files under the [design] page but user a separate plugin page where model/views/controllers/etc are organized by name. --------- Logically, I think the plugin should be organized as sub-folders (in admin). Physically, I am not convinced. The current mechanism only requires a convention. If plugins where physically in a subfolder then web2py would need major modifications to handle dispatching, bytecode compiled applications, be able to locate models, decide order of execution, etc. This would delay the project a lot and would make web2py slower. --------- Moreover some plugins may need to override normal web2py files, like layout.html, base.css, web2py_ajax.html, generic.*. etc. This cannot be done if the plugin is physically contained in a subfolder. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
