Fork me on GitHub
#reveal
<
2020-12-11
>
vlaaad20:12:41

love it!

😄 1
seancorfield20:12:47

@wilkerlucio (or @vlaaad) can you give a bit more background on what the state change stuff does for the web view? I noticed there was an example in the cljfx(?) repo that also had that...

wilkerlucio20:12:48

the way I understood it, the component props in JavaFX are the classic java beans style, and they have some observability capacity. and in cljfx we define some getters and setters that will change reactively to data coming to cljfx

wilkerlucio20:12:10

so those, state changes are a bridge on that, hooking on properties and also on listener/callback mechanisms from JavaFX

wilkerlucio20:12:21

but I believe @vlaaad can give a more accurate explanation

vlaaad20:12:37

As I understood per JavaFX docs, state-change is basically a callback when web-page is loaded

vlaaad20:12:29

there is no built in way in cljfx to listen for that state-change event, but cljfx is extensible enough for you to write custom props that allow bringing those event sources to cljfx event handling system

seancorfield21:12:10

So if you just want to display a basic web page, click links to other pages, submit forms, that can be done with the basic web view, but any sort of SPA style app needs the extension for state changes? (if you want to browse it internal to Reveal)

vlaaad21:12:27

You probably can browse SPA with basic web views as well. What's missing is a way to communicate between Reveal and the web page. I'm not sure this state change thing is enough for that. I want to explore this area soonish because I see a lot of leverage from being able to use and interact with browser visualizations

vlaaad21:12:35

A bit concerning that javafx's webkit does not work well with that graph library...

wilkerlucio22:12:17

yeah, I'm quite sad about that, but still, some comms with that can still cover a lot of cases