thanks for response - as I said, webpy has a good community and it's a
real plus when the core developers are actively involved on the list.
Some continuing questions/comments:
Anand Chitipothu wrote:
>> 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()
>
>
okay, I was thinking of the typical CRUD stuff: display(several), add,
edit, update,delete - from your response I guess it's simpler than I
thought - have the "action" parameter passed in as a series (which I
didn't realize you could do) and just split up with ifs under the
appropriate REST method (not that I'm a big fan of REST but everyone
else seems to be). Anyway so that does seem to be a simple way to keep
all the actions under one class. Maybe we should write up a "web.py for
Rails/Cake developers" :)
>> 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?
>
not sure what is "site" template but I just meant the templator template
used in display output (ie mako, jinja, ...)
>
>> 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()
>
this jogs my memory and I think we got this answer before so sorry - but
maybe we struggled with it versus the automatic joins in Active
Record/SQLAlchemy, etc. for a big 75 table app we were working on. But
the list approach may work well with some simpler table projects we are
doing. I guess if others are doing it in PHP, no reason it can't be
done as easily with Python lists. We'll take another look at web.py
for our new apps.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
