dynamoit VS SnapKit

Details you can find here https://github.com/bykka/dynamoit/blob/master/pom.xml

As for me Java is the main advantage. That is why I decided to use JavaFX for my project

Thought the same when started my tiny DynamoDB viewer but now feel a lack of some functionality that is available in Eclipse RCP

set of factory methods - https://github.com/bykka/dynamoit/blob/master/src/main/java/ua/org/java/dynamoit/utils/DX.java

I have developed a small AWS DynamoDB client using plain JavaFX https://github.com/bykka/dynamoit

You can find the release on GitHub.

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