rerun-io
Introduce re_table, implementing styling and basic table things
Related
- part of https://linear.app/rerun/issue/RR-2360/multi-selection-within-a-partition-table
What
Simplifies the datafusion table code by pulling out the fuctionality that doesn't need to know about datafusion in a re_table wrapper. It handles styling, column order / visibility and eventually row selection. For now I'll leave it in the datafusion table crate, in case we do find something in re_table that does require tighter integration with datafusion. But eventually it could become a separate crate, and be used for the dataframe table as well to add selection / row numbers / table config.
Web viewer built successfully.
| Result | Commit | Link | Manifest |
|---|---|---|---|
| ✅ | 8d6d067 | https://rerun.io/viewer/pr/11893 | +nightly +main |
View image diff on kitdiff.
Note: This comment is updated whenever you push a commit.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
- Is this maybe be a step towards https://github.com/rerun-io/rerun/issues/10575 ?
- Is this maybe be a step towards Replace uses of
egui_extras::Tablewithegui_table#10575 ?
Could be, maybe we could add a compability layer that adds a egui_extras like api to this. On the other hand, maybe that compability layer could/should exist in egui_table? Then we could deprecate and eventually remove the egui extras table