On Friday, December 2, 2016 at 12:33:46 AM UTC-8, Gabor Nyul wrote: > > Brian, > > In fact this is already done. I have a complete specification of each > report. > Just to give you an example: We are a railway company, having several > hundreds of train per day. There are a lots of modifications (above 60%, > Don't ask why) to the original plan where we are assigning the engines and > the staff. > The planning staff needs a report to see for the coming month all the > tracks and track segments, with all the statuses to be able to react > (definitely assign or remove/reallocate resources, etc.). > So from the UI point of view even the paging is bad as they have to > smoothly scroll among the data. >
I'm not sure SQLFORM has a limit to the number of rows it can display; you can leave off the limitby and give everything. You can do the same when supplying Datatables; using an external library allows you to use the additional features a dedicated UI toolmaker can provide. The transfer of data may be longer than you like, but you've probably already measured that, and it may be small compared to the stored procedures time. For a more reasonable download time (as a later enhancement, perhaps), ajax can be used to provide "smooth scrolling", such as you get when using Google Groups (the thread list view) or Google Image, or a bunch of other places. I think the Datatables site has an example of this, but it's been a while since I looked there ... my handful of users don't have a lot of slice-and-dice needs. /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 [email protected]. For more options, visit https://groups.google.com/d/optout.
