Ian Lyttle

This has got me going now.... Thinking now to change the API of the handler-builders: ```r vw_handler_data

Putting this off until next release - it turns out I went down this path two years ago, and what I came up with wasn't so bad. Thinking to dust...

Nothing comes immediately to mind - I got stuck because when we run from the R command line, we use V8 (node), which does not have `window` available. An alternative...

This could also be an opportunity to add some functions to help build signal patches: ```r patch

At one point, @sa-lee suggests that we transpile our javascript from typescript. I think this is a great aspirational idea.

As I approach the one-year anniversary of this issue, I wonder if there could be multiple Rmd files, and then one to run them all. We would need a `config.yml`...

As well, perhaps `infrastructure.Rmd` could write only to `inst/htmlwidgets/lib`, and we would have only one copy of `vegawidget.js` (`inst/htmlwidgets`). Perhaps `infrastructure.Rmd` could install `vegawidget.css`, but leave `vegawidget.js` where it is.

Hi @joelostblom, In the most-recent version of vegawidget, there's a function `vw_set_base_url()` that might be handy. It is written up in the most-recent Altair: Does this help this situation?

This will include a mini-manifesto, or set of principles.

Hi @saptarshiguha, I don't use jupyter Lab myself, but I wonder if the changes made in https://github.com/vegawidget/altair/pull/136 could be useful. I hope to have them merged soon, but you can...