I don't really want to have an javafx eventbus <-> vertx eventbus

@jkbbwr I don't know a lot about the code and how it works, I'm just refactoring. 😉

(That was more addressed at the rest of the channel)

great. I see that @carlw and @Ruckus are online, so maybe they can help?

no, i don't think i'd integrate vertx and javafx

@carlw Got any alternative suggestions?

you're trying for a rich internet web app?

No. Im trying for a UI for a console agent

this is to get the internals from Vert.x so that you can display them on the desktop?

both recall and do actions

I "could" run a local socket and run the agent and app seperated but not sure I like the sound of that yet

i like that decoupling more

ex, publish a heartbeat message to the socket via udp

websockets might be easier to code than raw sockets too

Id end up doing it dockersocket style if I were gonna do that

Does WebView support Airbnb's Lottie animations? This tiny demo won't render for me but I may be missing a step. https://codepen.io/atmospherix/project/editor/AQbjVx

Just means I gotta emulate request response over another transport ha

either request response or "fire and forget" if you're doing realtime

hmm

IMHO, i'd rather write the requirement in two stages: an off-the-shelf vert.x status producer (heartbeat on socket) and an off-the-shelf tornadofx consumer (read heartbeat, save heartbeats for time-based view, etc)

also, remember to secure the protocol

Quite.

Ugh, management want UIs. Development want more of the actual agent.

I wish I could tell management to go away

also, you could test the two pieces independently

LMK if you try to embed the app in vert.x. i'm getting a webapp client soon

LMK ?

let me know...i have teenagers 😀

The webapp client stuff will be simple for vertx.

So would this if I could just expose an attribute to the view