cljfx

https://github.com/cljfx/cljfx
jlmr 2020-02-24T07:17:07.001300Z

@vlaaad hi again, is there a way for :renderer-error-handler to know where in the fx-graph the error occured?

vlaaad 2020-02-24T07:28:54.001400Z

Hi! Unfortunately, there is no way to do that.

vlaaad 2020-02-24T07:33:16.001500Z

I understand that it's frustrating, I don't like it too. I thought a bit about the idea of inspector for javafx nodes and cljfx graph, but haven't come up with anything yet. What might be worth exploring is custom debugging fx->lifecycle middleware function that wraps all fx lifecycle with something that allows some kind of introspection. Your use case seems to be expressable with this middleware

jlmr 2020-02-24T09:20:50.004700Z

Looks like something I will look into when I have a bit more time. Thanks for the tip!

EmmanuelOga 2020-02-24T07:37:44.002400Z

out of curiosity, does cljfx work by creating fxml by any chance?

EmmanuelOga 2020-02-24T07:38:31.003300Z

not sure if it does that or maps the specs to javafx objects directly

vlaaad 2020-02-24T07:38:45.003400Z

No, it is more of a replacement for fxml — more dynamic and clojurey. Cljfx does not depend on fxml at all

vlaaad 2020-02-24T07:39:25.003600Z

It maps props to objects directly

EmmanuelOga 2020-02-24T07:39:41.003900Z

ah ok

vlaaad 2020-02-24T16:56:57.004900Z

For your information, guys: I'm currently developing Reveal tool (Read-Eval-Visualize Loop), it's built on top of cljfx. There is a repo: https://github.com/vlaaad/reveal and a channel: #reveal

2020-02-24T22:28:38.005400Z

@vlaaad awesome!