Ryan, You're right !, I want to do this, or be, modules, but I think that plugins can be a best approach. IMHO a plugin architecture can aggregate more value to web.py For example, a plugin to RSS, a plugin to gallery, a plugin to polls, a plugin to calendar/agenda, a plugin to banner publication, but I know that this approach isn't the main goal of this framework. The main goal of web.py to be simple and easy, but looking in the cookbook section I see that it's so complete, ever that I seek about a example code (to solve a problem that I have)... I have a answer in the cookbook.
In my country (Brazil) many python developers think that the web.py is a mini-framework, but I don't agree with this opinion, I think that it's very complete. IMHO, to be better ... it needs two things: 1) A standard way to develop a project with web.py, by looking in the sources in various projects that I found in GIT(or another repo) each project developed witg web.py follow a way, a structure, no there a standard in the structure of a project. 2) A plugin architecture. But, thank you so much ! -- You received this message because you are subscribed to the Google Groups "web.py" group. To post to this group, send email to webpy@googlegroups.com. To unsubscribe from this group, send email to webpy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/webpy?hl=en.
