> 1) found the controller class scheme confusing - ie if we have customers
> and we want a page to display a table, another page to display a graph -
> it seems we have to write 2 classes with get functions - instead of a
> customer class that has a listing function and a table function.
urls = (
"/data/(graph|table)", "data"
)
class data:
def GET(self, type):
if type == "graph":
do_graph()
elif type == "table":
do_table()
> 2) didn't like the default template but seems to be easy enough to
> change to more popular jinja (django, werkzeug, rails-like)
default template?
Do you mean the site template?
> 3) ran into trouble with the db iters - seems you can only pass thru the
> list once yet in our pages we often have to pass thru or access more
> depending on the display modules.
you can call .list() on the iter to get a list.
result = db.query('....').list()
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web.py" 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/webpy?hl=en
-~----------~----~----~----~------~----~------~--~---
