I much prefer an exposed event loop and Command objects. This is kinda how a browser's event loop is implemented. My bestie George Smith's Juipeter (?) took the Win32 API approach, preserving the Swing API and all dispatch was handled under the hood.
Install4j gpu option code#
Meaning all modifications are handled by the framework, no client code (or non event loop threads) can modify the UI. (I haven't done Swing work in ages, so maybe this happened.)Īn event loop is the biggest thing missing from Swing and other UI toolkits of that era. By the time I created enough shims to make Swing truly composable, I wish I'd started from scratch. In my own noodling, Swing's UI component hierarchy needed to be refactored to be fully composable. But maybe 40%-50% of the framework could be safely removed. I don't think Swing's MVC strategy worked out. So if someone said "build a usable high-quality GUI asap or you die" to me, I'd go to Swing immediately. And I think the community, as a whole, just understands it less (less prior art etc). That said, I think it did have a slightly higher O() for frustration than Swing's O(1). I love-love-love using SceneBuilder for designing the view layer and the Observable pattern, I think, yields a lot of nice QOL/verbosity-reducing things. I have a personal project that was originally in Swing and I ported it to JavaFX because HiDPI is in a lot better shape there (though I think Swing has since figured it out?). but for internal tools where you have a lot more leverage over the environment, I think it looks extremely attractive.
Install4j gpu option software#
So it's definitely a no-go for your actual software product. Imo that's really where the web won - certainly not because of its dev productivity. The biggest hurdle I see nowadays to using Swing is all about distribution: both of the jvm and the program. In my imaginary company that I own where we all run linux laptops that are managed by puppet or something, I think we might make a strong case for building many internal tools in Swing. One of the best feelings in the world is replacing a complicated nesting of buggy BorderLayouts et al with one nice (slightly verbose) GridBagLayout that actually works. Whereas CSS are absolutely O(n) or worse.
Maybe I'm just warped but GridBagLayout, while containing a certain base level of frustration, is O(1) for frustration. "There are Swing developers with low pain tolerances?") it's astonishing how productive Swing feels compared to React even so many years later. I have a long history with Swing and as painful as it is to use sometimes (e.g.
0 kommentar(er)
