SnapKit VS tornadofx2

SnapCode is actually using SnapKit (https://github.com/reportmill/SnapKit) which can run on either WebAPI/DOM (in browser) or Swing (desktop). In the browser this helps slim the download and improve performance by using more browser native code.

For pricing, SnapCode is free for individual use and will remain so. Perhaps there will be funding opportunities from large organizations or for embedding use cases to help provide for the continued health of the product and community.

The new kid on the block is SnapKit: https://github.com/reportmill/SnapKit

Theres a bit more to it than that, since you want resetUI to update all of your components without triggering respondUI(). And you want all your components to be automatically configured to call respondUI() when there is user interaction.

I’ve written one of these before, but I don’t have access to a public version anymore. I do all my current UI dev in a UI kit built on top of Swing. But here is what I use there that solves this problem:

https://github.com/reportmill/SnapKit/blob/master/src/snap/v...

I use SnapKit to do Java desktop development which compiles easily to JavaScript using TeaVM. SnapKit is both modern and conventional, a good middle ground between Swing and JavaFX. But most importantly, it combines the traditional win of desktop Java UI dev with the ease of web deployment.

    SnapKit: 

Repo: https://github.com/reportmill/SnapKit

I have seen some scattered advice against it, but the syntax seems nice. A port for java 11+ is also available: [TornadoFX 2]{https://github.com/edvin/tornadofx2}

It is great, but pretty much abandoned. Edvin the original author is still around, answering questions and ready to make releases. But he is not going to develop it further. There were some contributions from community to https://github.com/edvin/tornadofx2 but negligible at this point.

Have a look at https://github.com/edvin/tornadofx2

I don't use TornadoFX but it looks like the author is continuing TornadoFX here: https://github.com/edvin/tornadofx2

Another point. The referred Badass plugin required java 11. And the current stable published version of Tornadofx requires java 8. There is another branch that supposedly works for JDK 10 and beyond. There is also another repo called tornadofx2, but it is not maintened. I think Edvin decided to keep with gis original repo. There are other ways to wrap a jvm application inside a native executable, though.