Show HN: Smart-table-scroll – Browser-based tables with 1M rows
1–10 of 19 posts
Re: Show HN: Smart-table-scroll – Browser-based tables with 1M rows
#2I've used Facebook's FixedDataTable too, which is also performant and relatively minimal, and it was also moderately painful to achieve even quite simple things.
Re: Show HN: Smart-table-scroll – Browser-based tables with 1M rows
#3Re: Show HN: Smart-table-scroll – Browser-based tables with 1M rows
#4Re: Show HN: Smart-table-scroll – Browser-based tables with 1M rows
#5The basic premise was ala google maps, a view port div, a massive div (map) within the view port for the scrollbar support, the concept of a virtual buffer area around the viewport and then a collection of tiles (tables) that would have data rendered into them and then be appropriately positioned into the buffer area around the viewport as one scrolls. Works well, have tested up to 40mm rows and columns and works in ie8 up to 4mm rows. Also supports random column and row sizes littered throughout the sheet. This solution does also break native in browser search though as mentioned in other comments.
Re: Show HN: Smart-table-scroll – Browser-based tables with 1M rows
#6What would be your use case? Apart from this being a nice feat of technology and the possibility of loading the data asynchronously, in what scenario would it be practical to present 1K+ rows of data to a user? It's infeasible or at least very impractical to examine them by hand - some sorting/filtering possibility is necessary for large datasets and if your filters still return 1K+ rows you could have filtered on so…
I recently had a scenario where I needed to have a table that could be scrolled, and needed to be able to display up to 15k rows.
At the time I went with SlickGrid[1], but this seems like a nice alternative.
Re: Show HN: Smart-table-scroll – Browser-based tables with 1M rows
#7What would be your use case? Apart from this being a nice feat of technology and the possibility of loading the data asynchronously, in what scenario would it be practical to present 1K+ rows of data to a user? It's infeasible or at least very impractical to examine them by hand - some sorting/filtering possibility is necessary for large datasets and if your filters still return 1K+ rows you could have filtered on so…
Edit: Seems like it might break on-page find though, right?
Re: Show HN: Smart-table-scroll – Browser-based tables with 1M rows
#8What would be your use case? Apart from this being a nice feat of technology and the possibility of loading the data asynchronously, in what scenario would it be practical to present 1K+ rows of data to a user? It's infeasible or at least very impractical to examine them by hand - some sorting/filtering possibility is necessary for large datasets and if your filters still return 1K+ rows you could have filtered on so…
I think it is more trying to show that it can handle & display extremely large datasets without crashing or lagging the browser. I recently had a scenario where I needed to have a table that could be scrolled, and needed to be able to display up to 15k rows. At the time I went with SlickGrid[1], but this seems like a nice alternative. [1] https://github.com/mleibman/SlickGrid
Re: Show HN: Smart-table-scroll – Browser-based tables with 1M rows
#9Re: Show HN: Smart-table-scroll – Browser-based tables with 1M rows
#10What would be your use case? Apart from this being a nice feat of technology and the possibility of loading the data asynchronously, in what scenario would it be practical to present 1K+ rows of data to a user? It's infeasible or at least very impractical to examine them by hand - some sorting/filtering possibility is necessary for large datasets and if your filters still return 1K+ rows you could have filtered on so…
An example I can think is a web based interface for controlling a drone. This could be used on the page to store the timestamped output of various sensors.
It would allow for the data to be displayed while also maintaining a history of the data in the browser. Could add in filters and searches as well as a pause functionality to review the historical data.
Sort of like a dmesg for the web page. I'm thinking practical uses are sensor monitoring and server monitoring.