3 ms·
From the article: "The road to high-quality UI on JVM is a long one. We’ll need: a graphics library, a window/OS integration library, a UI toolkit. Today I am
by hutzlibu 6y ago
From the article:
"The road to high-quality UI on JVM is a long one. We’ll need:
a graphics library,
a window/OS integration library,
a UI toolkit.
Today I am happy to announce the first part of this epic quest: the graphics library"
Maybe you misread a bit? I do not see him suggesting, to use his first step for the UI. The idea is to build the UI kit on top of it.
- saagarjha 6y agoI get that, it’s just that this is being presented as something that will kill Swing and Electron, which obviously makes it so that many will take away “I should use this to draw my buttons” from it. I’m advocating caution before throwing away Swing right now.
- hutzlibu 6y agoWell, his intention is to create something that will eventually kill Swing (and Electron), so he probably got carried away wih his words a bit, but I do not see him missrepresenting.
- mmm_grayons 6y agoThis is a blog post, not a product launch. It's intended to be a foundation on which a "real" GUI library can be written. The author mentions that it is one of several steps that should allow the Java community to coalesce around a better toolkit in the long term.
- geokon 6y agoI think it's confusingly worded b/c they compare to Swing and JavaFX in the first lines - so it sounds like this is aiming to replaces those. But in-effect this is just a first step towards that larger goal. Why the graphics library needs to be rewritten from scratch and they couldn't implement a better UI toolkit on top of what already exists is left unanswered - and that's confusing. All it says is "Java UI progress was blocked by the poor-performing Graphics2D"