Imagine the web if every site was exclusively tabular. No UIs just a table of figures and a CRUD for modifying it. Something like hypercard meets excel
Ah… the good old spacer.gif days…
The design philosophy of Great Tables
31–40 of 94 posts
Re: The design philosophy of Great Tables
#32Re: The design philosophy of Great Tables
#33Re: The design philosophy of Great Tables
#34Regarding “nanoplots”: they are essentially sparklines, aren’t they?
Yes. They are sparklines. I actually asked Rich the author if they should just be called that in great_tables but he had some reasonable thoughts on why a distinct name made sense.
Re: The design philosophy of Great Tables
#35Summary: This article is about a Python library called “Great Tables” that is focused on the display of tables for publication and presentation (not for interactive browsing). The article does not specify which output format it supports. Also you get some bonus historical context on tables.
... the obligatory "historical context" nobody asked for.
Re: The design philosophy of Great Tables
#36It's great that the RStudio team is working on Python libraries. Hope to see dplyr and ggplot someday on Python.
plotnine is a ggplot also funded by Posit (though, externally developed) https://plotnine.org/
I use plotnine whenever I need to make (static) plots in Python. It's really quite well done, a close match to R's ggplot2, and more feature complete than any of the other Python grammar of graphics packages I've tried.
Re: The design philosophy of Great Tables
#37Not mentioned yet are DocBook tables, of which there are several types. The kind we used starts here: https://tdg.docbook.org/tdg/5.1/cals.table. You have to drill down to get inside the tables. They have some--but I think not all-- the structure of GT.
There's also of course LaTeX (mentioned in a couple other comments here), which has "ordinary" tables and long tables (tables that span more than one page).
Re: The design philosophy of Great Tables
#38The example they show of a Great Table is, to my taste, way too busy. Here is my unsolicited opinion: The top and bottom horizontal rules on the Title appear to be superfluous, and I dislike how it is aligned with the first column (row labels) rather than the second. I feel like a little space to breath at the bottom, along with a bold font would add visual hierarchy w/o the clutter. The row label backgrounds are far…
I don’t understand why there aren’t any horizontal rules or stripes etc to reinforce the idea that each row is its own record.
Re: The design philosophy of Great Tables
#39How does this compare to https://github.com/jieter/django-tables2? That one makes it really easy to display database models as HTML tables with column sorting and pagination, and search/filtering can be added on top with django-filter.
Re: The design philosophy of Great Tables
#40The example they show of a Great Table is, to my taste, way too busy. Here is my unsolicited opinion: The top and bottom horizontal rules on the Title appear to be superfluous, and I dislike how it is aligned with the first column (row labels) rather than the second. I feel like a little space to breath at the bottom, along with a bold font would add visual hierarchy w/o the clutter. The row label backgrounds are far…
Keep going IMO: shorten the title to remote correspondents since the rest is redundant with the column names. The blue highlight is now redundant with the title so ditch all of it. Personal characteristics vs location don’t meaningfully improve the organization so ditch those as well.