I think I agree with Thadeus in his exposition, this way we could implement a quickly "module setup page" for applications where you can choose install uninstall modules inside applications.
Another thing: What about a plugin designed to overrides views/layout.html or views/ web2py_ajax.html or static/base.css? It would not be possible. You would not be able to use your proposed structure to create a plugin that applies a layout to an existing app. Massimo, maybe we could clear up plugin system if we could distinguish between Plugins and Themes? where themes could be installed the same way but based on overrides/extend some html/views/layouts? this way folder structure would remain: - application > --cache > --controllers > .. > --models > --modules > .. > --plugins > ---myplugin > ---myplugin2 > --views > --themes > ---default > --web2py_ajax.html > --... > ---mytheme > ---myothertheme Just some thoughts, Alex El 29/12/2009 19:25, Thadeus Burgess escribió: >> If plugins have models in their own folder, then should all models be >> executed when a non-plugin controller is called, including plugin >> models? If so, there would be a lot overhead to new directory >> structure. Moreover in which order would they be executed? Whatever >> you choose would not be obvious. If plugin modules where only to be >> executed when plugin controllers are called then they would be >> accessible by appadmin and they would have very limited functionality. >> for example they would not be able to act on non-plugin modules. >> > This is why django has... > > installed_applications = [ > 'contrib.auth', > 'my.blog', > 'comments', > ] > > Which solves this problem. Its just one more line in db.py (or settings.py), I > already have to declare admin, why not installed_plugins = [] ?? then > web2py will go through the plugins in that order, create their models, > etc etc... > > For another example, I view Auth, Crud, Mail etc... as 'plugins' that > happen to be included with web2py always > >> For me a plugin is just a subset of an app that you can >> extract from an app and you can apply over an existing app. >> > I think we've been trying to get this out of you for quite some time now :) > > So what you call a plugin, is not what I call/imagine a plugin. > > -Thadeus > > > > > > On Tue, Dec 29, 2009 at 9:40 AM, mdipierro<[email protected]> wrote: > >> If plugins have models in their own folder, then should all models be >> executed when a non-plugin controller is called, including plugin >> models? If so, there would be a lot overhead to new directory >> structure. Moreover in which order would they be executed? Whatever >> you choose would not be obvious. If plugin modules where only to be >> executed when plugin controllers are called then they would be >> accessible by appadmin and they would have very limited functionality. >> for example they would not be able to act on non-plugin modules. >> >> > -- > > 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. > > > > -- Alejandro Fanjul Fdez. [email protected] www.mhproject.org -- 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.
