can you create a module and/or a base template that you can put the "boilerplate" code in so you don't have to duplicate the stuffs in each individual controller and view? or can you write a generic controller that based on parameters/POST data adjusts its queries.
On Thursday, December 5, 2013 12:32:06 PM UTC-8, Jim S wrote: > > Looking for advice here. > > Traditionally I've used SQLFORM.grid when I want to have a list where > people can select what record they want to work with. That works fine for > me but a new app on working on has a requirement to have it's list pages > look more like a google search results page. No table like features like > headings, columns, etc. Just one list with a header row and a variable > amount of data below it. > > I don't have a problem creating the page, but am not sure the best way to > implement the paging controls. I've got the functionality all working > based on > http://web2py.com/books/default/chapter/29/14/other-recipes#Paginationfrom > the book. However, seems like a lot of boilerplate code I need to put > in each of my list controllers (there around 20 of these list controllers). > > > Wondering how others have handled similar requirements and would > appreciate comments from anyone who wishes to share. > > Thanks! > > -Jim > -- 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
