In my mind a plugin is a w2p file that (xxx) contains a subset of the following files/folders:
models/plugin_xxx.py (it does not have db=SQLDB but assume a "db" object is available) controllers/plugin_xxx/* moduels/plugin_xxx/* static/plugin_xxx/* views/plugin_xxx/*.html views/layout.html (optional for layout plugins) plugin_xxx.README There should be a way for the plugin to publish what it does so that menus can automatically update, but you do not need this now. Massimo On Jun 17, 10:52 am, Philip Kilner <phil.kil...@gmail.com> wrote: > Hi Massimo, > > mdipierro wrote: > > I think this is a great idea. > > Have seen your comments in earlier threads when you state that you don't > want to burden web2py with too much stuff by default, and I can see the > logic of that. However, the Theme Roller tool is so useful that I want > to have the option to use it as simply as possible, and I want to share > my solution if I can figure out how to package it. > > > Right now a web2py w2p always contain an entire app. It does not have > > to be that way. > > A w2p may contain a subset of an up (plugin?) and be unzipped over an > > existing app to change some, its layout for example. > > That was what I hoped - better to have a way of dropping the themed > version in without changing an existing app if possible. I'm still > learning with web2py and don't want to get too far off the beaten track, > so my first step will be to build an application that I can use as a > staring point. > > > In my view a layout w2p would look like this: > > views/layout.html > > static/plugin_name/required_static_files > > Makes sense... > > > It would be easy to modify admin to handle installation and rollback > > of plugins. > > ...but how to treat an application as a plugin (or the difference > between the two) is what I need to understand next. > > Is there any documentation focussed on plugins as opposed to > applications? I haven't found any yet, but am not sure that I've been > suing the right terms... > > > I do not know if modifying web2py_ajax is a good idea or not becase > > some users may need web2py_ajax but not ThemeRoller. Perhaps we want > > two ajax files. I would want to see which changes are required before > > deciding about this. > > I agree that it is not wise to modify web2py_ajax - I've created a file > called web2py_jquerygui (horrible name - will make it > web2py_themeroller!) with my changes. The only file I think I must > change/replace is base.css, so that I have the right styles on the menu. > > I'll mail you my ThemeRoller application once it is presentable - but I > suspect that I'll have more questions before that! > > -- > > Regards, > > PhilK > > 'work as if you lived in the early days of a better nation' > - alasdair gray --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" 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 -~----------~----~----~----~------~----~------~--~---
