baptiste
baptiste
if I think of a `gtable` as a `data.frame` rather than a `matrix`, then locating (a) grob(s) is like applying `subset()` with `t, b, l, r` and/or `names`.
locating and removing grobs is definitely a useful feature to have, see how messy it gets in this example: https://groups.google.com/d/msg/ggplot2/87gdDq0P3x0/WZxs89AY1HwJ
I'm not familiar with the rendering pipeline but I imagine it'd be relatively straightforward to adapt SVG or canvas primitives to their [roughjs equivalent](https://github.com/rough-stuff/rough#usage). The theme would only need to...
I kind of have something along those lines in egg::geom_custom but it's not on CRAN because it requires a newer ggplot2
privately – I regularly get sick of random "issues" posted by strangers. The idea is to use list-columns to map grobs (or arbitrary data to draw a grob) as a...
or maybe [minisvg](https://github.com/coolbutuseless/minisvg#stag-helper-autocomplete-svg-element-creation) stag?
The way standard grobs work (not sure it applies directly to svgparser's ones) one could imagine the SVG being generated at drawing time, e.g. here each pie plot doing something...
I was playing around with `fontr` to turn glyphs into polygons, and decided to try the drawDetails thing on a SVG string create at draw time. I think it can...
grr
@maelle i'm keen, but broke my right arm last weekend so typing is a bit of a struggle