SnapKit

I think Swing is a non-goal of this project. It provides good interop with the DOM and core JS methods, and it makes it easy to create your own interop for JS apis that aren't in the core. There are at least two GUI toolkits that run on TeaVM: 1. Codename One. Similar to swing, but focused on mobile https://www.codenameone.com 2. SnapKit. Targeted at desktop. Also a light-weight toolkit, like Swing. https://github.com/reportmill/SnapKit

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.

I think the biggest flaw of Swing is that it didn’t provide or promote a standard ‘Controller’ class. I have seen tons of Swing code over the years that is a spaghetti code mess of UI creation, initialization, updating and responding. So my big tip is to create a SwingController base class for any of your UI panes with the following methods: - JComponent createUI(); - void initUI(); - void resetUI(); - void respondUI(Event anEvent); 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 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: https://github.com/reportmill/SnapKit Demos: https://reportmill.com/snaptea/ Disclaimer: I am the primary author, so this is self-serving. But it doesn't mean it sucks. :-)

GitHub: https://github.com/reportmill/SnapKit Demos: https://www.reportmill.com/snaptea/

If Java had a modern UI toolkit to create & run apps natively on the desktop and in the browser, could it rescue Java Client development? I've been working on SnapKit for several years (+) to rescue my apps from obscurity by deploying in the browser and it's gone reasonably well, so I'm wondering whether it could be more: GitHub: https://github.com/reportmill/SnapKit Demos: https://www.reportmill.com/snaptea/ jeff

I am working on a Java UI kit that works on both desktop and browser: Demos: https://www.reportmill.com/snaptea/ Repo: https://github.com/reportmill/SnapKit There is a lot of benefit to this - fast, traditional desktop development with great deployment. It also has built-in developer tools and online access to a UI Builder. I hope this could make Java Client development interesting again. I need collaborators to help write demos and improve the kit. Jeff at ReportMill dot com

Nope - it works everywhere: https://github.com/reportmill/SnapKit