I believe that a "real" web2py plugin system is going to require changes to the base web2py code. Otherwise its just a nifty trick.
Plugins would need to be self contained, and not pollute the rest of the system. Plugins can be passed variables., for example, lets say you have a Star Rating plugin, and you need to display multiple star widgets on a page, then you would need to pass a UUID to the star widget so it will know which one to display. Plugins will need to be completely customizable, meaning you can call different parts of a plugin at any time. So with the star widget plugin, you could either call the actual DOM representation (which includes the <ul> of <img>) or you could just get back text that represents the average score. Now for including the new web2py_ajax in trunk. I agree, its nice to have for now, although I doubt I would be using it. On the naming convention... Sure, I don't think it really matters much, since anybody can use something different if they wanted. -Thadeus On Fri, Oct 2, 2009 at 7:35 PM, suiato <homm...@gmail.com> wrote: > ch component augments its corresponding model, controller, or view > of applica > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
