So, documentation should be improve!! Alone dev practices Team dev pratices
Examples What should go where Richard On Mon, Feb 9, 2015 at 10:43 AM, Carlos Cesar Caballero Díaz < [email protected]> wrote: > > Can you point to an example of a query in the book that you think should > instead have been shown in a model? > > > All of them, or at least mention that queries should go in controllers, > even a simple query, will represent a problem, if we need to change it and > is used many times, new users, that read the image blog and simple wiki > examples, should explicitly known that in web2py, the recommended way is > putting the queries in models (or modules), all this in my opinion of > course. > > Of course, if you are working with designers who don't know and are not > interested in learning Python, it makes sense to keep as much as possible > in pure HTML. But that is not the only context within which web2py is used. > If you don't want to use the HTML helpers, you don't have to, but that > doesn't mean they should not appear in any book examples. > > > We are moving away a bit from the main point, imagine that I made an > application and my designer is learning how web2py views work and how > helpers are used (which is exactly what is happening to me now), my > designer does not have to look at the controllers, that is the goal of MVC > , if I'm going to make changes in views, I do not have to know what is > happening in the controllers. In the example that i mentioned, how I ask > to a designer that modify a view that says: > > {{extend 'layout.html'}} > {{=form}} > > Web designers normally know html and css, and if there is a way to easily > separate views and controllers, then web2py is going to be easily adopted > in teams with specialized members. But if I read in the main doc examples > with view related code in controllers, then I not adopt the framework. > > > > When I started web2py also started with web development. But now, with the > little experience I have, if I started from scratch using python, and read > the book of web2py, I would go for another framework (Just after the > Overview chapter), and would be a shame, because the documentation does > seem to web2py one thing that it's not > > > -- > Resources: > - http://web2py.com > - http://web2py.com/book (Documentation) > - http://github.com/web2py/web2py (Source code) > - https://code.google.com/p/web2py/issues/list (Report Issues) > --- > You received this message because you are subscribed to the Google Groups > "web2py-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
