`tinytable`

[vincentarelbundock]

Thanks for sharing such an interesting and powerful package!

This is a proof of concept to add support for tinytable, a dependency-free package to draw tables. By implementing a reasonably simple tt.rtables() S3 method, we get:

1. Powerful styling functionality (colors, sizes, underlines, rules, bold, italic, etc.)
2. Output to HTML (static or interactive w/ filtering, etc), LaTeX, Typst, PNG, markdown (grid and gfm), and (limited) word.

Here's a gist with the code I used:

https://gist.github.com/vincentarelbundock/d81251cea8ed99ffd3f40546b4ab663b

And here is the rendered HTML:

https://arelbundock.com/rtables_examples.html

Here is a simple example:

library(tinytable)
library(rtables)
source("rtables_to_tinytable.R")
lyt1 <- basic_table(
  title = "Summary Statistics by Treatment Arm",
  main_footer = "Data from clinical trial") %>%
  split_cols_by("ARM") %>%
  analyze("AGE", function(x) {
    in_rows("Mean" = mean(x), "SD" = sd(x), "N" = length(x), .formats = c("xx.x", "xx.x", "xx"))
  })

tbl1 <- build_table(lyt1, ex_adsl)

# Convert to tinytable using tt()
tt(tbl1) %>%
  style_tt(i = 1, bold = TRUE, color = "white", background = "#2C5F8D", fontsize = 1.3) %>%
  style_tt(i = 2:3, background = c("lightgrey", "lightblue"))

[vincentarelbundock]

Here's an animated gif to show how flexible tinytable can be.

[shajoezhu]

dear @vincentarelbundock , tinytable looks awesome! I was wondering if it is more practical to include your scripts into tinytable? and list rtables as a suggested package? i was able to open your gist file, but not anymore.

[vincentarelbundock]

Thanks for taking a look!

My goal with tinytable was to design a dependency-free package to make it cheap/easy for other package maintainers to add a single dep, and get super flexible tables.

Tables are something that a lot of packages require, so it feels like a slippery slope to add support for (potentially dozens) of upstream packages, all supported by me.

So I think it would make more sense to go the other way from what you suggest.

But of course, if you don't need/want fancy styles for HTML/LaTeX/Typst/etc., it doesn't make sense to work on this on your end either.

If you are interested in these features, I'd be very happy to help integration. Otherwise, feel free to close this issue. Not a big deal at all!

[vincentarelbundock]

Thanks for taking a look!

My goal with tinytable was to design a dependency-free package to make it cheap/easy for other package maintainers to add a single dep, and get super flexible tables.

Tables are something that a lot of packages require, so it feels like a slippery slope to add support for (potentially dozens) of upstream packages, all supported by me.

So I think it would make more sense to go the other way from what you suggest.

But of course, if you don't need/want fancy styles for HTML/LaTeX/Typst/etc., it doesn't make sense to work on this on your end either.

If you are interested in these features, I'd be very happy to help integration. Otherwise, feel free to close this issue. Not a big deal at all!

[shajoezhu]

hi @vincentarelbundock , i like the latex feature! and I would like to collaborate. there are a few things that I on my mind.

1. we use these packages for clinical reporting, and going through a rather heavy complex validation process at the moment (there is working progress to ease this process in the future), but right now, i am inclined not to include this as an upstream dependency, even if in suggests, we will need to check, i think in near future, we can include this feature.
2. i have a proposal to create a new package tiny.rtables or some sort, to host these code, which has upstream depends on rtables and tiny table. what do you think? just a small POC for now
3. gsk had worked on table latex replated package, https://github.com/GSK-Biostatistics/docorator, i know quite different, but just fyi,