Table-generator: Overview level #423
Labels
Comments
|
can I take up an issue please |
PhilippWendler
added a commit
that referenced
this issue
Nov 2, 2019
This provides a complete rewrite of the HTML tables that `table-generator` produces. Instead of statically creating a HTML `<table>`, we now insert the data as JSON and use [React](https://reactjs.org/) to render a table dynamically. Furthermore, all the spaghetti code for interactive features like plots is now completely replaced by a proper architecture using React components, and there exists infrastructure to test this. Some new features like better row filters and improvements have also been added based on a user study. But the main advantage is that it is now possible to open large tables in browsers without long waiting periods. The studies and the rewrite were done by @bschor and a report about this is available as her [Bachelor's thesis](https://www.sosy-lab.org/research/bsc/2019.Bschor.Modern_Architecture_and_Improved_UI_for_Tables_of_BenchExec.pdf). Users who whish to continue using the old tables can pass `--static-table` to `table-generator`, but we expect this to be removed in BenchExec 3.0. Fixes #130 (sorting added) Fixes #423 (summary tab with only header and footer of table added) Closes #123 (all Javascript is now bundled in the HTML file) Closes #195 (all Javascript is now bundled in the HTML file) Closes #214 (filtering is now longer in an overlay, and much faster anyway) Closes #237 ([react-table](https://www.npmjs.com/package/react-table) is used) Closes #296 (main table has only small header, full header is shown on summary tab) Closes #297 (main table has only small header, full header is shown on summary tab) Closes #375 (no longer applicable)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, for a given set of benchmark-results (XML files),
table-generator generates one huge table.
The large tables are nice to have a look at details,
however, for getting a quick overview, they are too slow to load.
It would be nice to have, in addition, an overview table (dashboard view) generated
that presents a coarser view on the benchmark results.
First proposal: Omit all results rows, and most of the header, and print only the bottom statistics.
One statistics block for each column (benchmark tool or configuration) and for each vertical block as well (if the input table definition has a
union).Either always written (like the csv currently) or only if an extra parameter is given.
The text was updated successfully, but these errors were encountered: