do you use reveal as a REPL?

if yes, use (r/open-view {:fx/type …})

if not as a REPL, use #reveal/inspect {:fx/type ...} for inspector popup

or, if you don’t use reveal as a REPL, but use one window where you want to open the view, use (r/submit-command! (r/open-view {:fx/type ...}))

if you do some sort of iterative progress on a particular view that you have in a def, you could also use observable-view to watch the var holding the view. Then, you can open the view once and iterate on defed value while the view will update automatically…

here is a demo of observable-view watching the var the holds a vega visualization data https://youtu.be/lqb4XlFI-08?t=1568

This is really helpful @U47G49KHQ. I too have been doing the manual flow Celio described. It'd be awesome if this knowledge was documented somewhere 🙂

It's mentioned there https://vlaaad.github.io/reveal/#built-in-components

I probably should write another blog post..

Or even do a video..

Or both..

A post on how you develop reveal would be awesome.

Sorry for the delay. Thanks so much for the info! Yeah I was reading the docs before, trying to make sense of the built-in component fns. I think the missing piece for me was to understand the submit-command! + open-view combo (I don’t use reveal as a repl). I’ll also check out observable-view, seems useful to my workflow.

> I probably should write another blog post Maybe a short section in the docs on development workflow?

Not sure it can be short given how many ways there are to use reveal...

I had similar problems when I played with building new views. Maybe a “common patterns” section would help in the docs. also breaking out the docs for “extending reveal” into its own page might help