The table should reference files that will be small, but may be used as a basis (perhaps in all possible combinations) for the creation of more files. So essentially the table should be used for streaming and adding records, ideally with extensible row customization for other features.
While powertable was easy to start up, my selection appears to be down to SlickGrid or HandsonTable, thanks to your reference. With little javascript/json experience, I have been trying to initiate a SlickGrid table (the difficulty being to initiate the grid in the proper scope so that both the table functionality and data are implemented). I have an unanswered post in the SlickGrid forum. Thank you for your response, as is helpful to provide some traction given the beginning phase I'm in. On Thursday, July 23, 2015 at 1:03:23 PM UTC-5, Dave S wrote: > > Datatable rather than Powertable seems to be the common tool discussed > here. > Massimo has enthused about HandsonTable > <URL:https://groups.google.com/d/msg/web2py/3IZ8uEAAXyU/FBZqaPh_aGYJ> > > Evidently you expect your users to be looking at lots of data. But it > would perhaps help us help you > for you to elaborate on what the "use case" is that you're working on. > Will users be viewing or editing? > Will users be adding records? Exporting the data for use elsewhere? How > many fields? > Will typical queries return thousands of records? > > Good luck! > > /dps > -- 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/d/optout.
