I was really disappointed about Datatables not managing correctly more then one instance of table in the same page... Problem with Datatables, is that it not supports the export button to work on more then once instance of datatables init per page if you choose to put your tables into tabs with jQuery UI tabs... So you have to choose between export feature or put your differents tables in differents tabs...
I was really happy to see that Web2py was implementing nice grid and thought that it will support any number of instance per page. I have to display on the same page more then one table for related data that not share the same amount of columns... I would prefer to not have more pages because data are directly related and adding entry in the menu will bring rapidly the app to be difficult to navigate (there is already a lot of entry in the menu). Hope the problems describes here could find a solution soon... Richard On Tue, Oct 11, 2011 at 2:20 PM, apple <simo...@gmail.com> wrote: > ....also slightly frustrating is that the add/view/edit pass the table > name so you can generate output based on that. However the paginate > buttons do not pass the table name. So if you have a controller that > dynamically creates grid parameters depending on the table then this > does not work with paginate. Would it not be more consistent to pass > the tablename with all the buttons? > > > On Oct 11, 7:12 pm, apple <simo...@gmail.com> wrote: > > Surely there must be a solution to this? It does not seem logical to > > have a component that is arbitrarily restricted to one per page? > > > > iframe is not a good solution. And I don't think LOAD with ajax works > > with multiple grids and pagination - certainly it does not work in my > > application even after the recent fix in trunk. I have got multiple > > grids to work with LOAD and no ajax, including the add/view/edit but > > not pagination. > > > > Surely there are many possible solutions to this without compromising > > the URL benefits you mention. For example you could include a "gridid" > > in request.args or request.vars; maybe also save the grid parameters > > in session. > > > > On Oct 11, 3:44 pm, Anthony <abasta...@gmail.com> wrote: > > > > > > > > > > > > > > > > > On Tuesday, October 11, 2011 9:49:51 AM UTC-4, stefaan wrote: > > > > > > (workaround: e.g. use iframes, or design a better UI that doesn't > need > > > > two grids in one view ;) > > > > > Using ajax components might be better/easier than iframes. >
