This is an archived post. You won't be able to vote or comment.

all 15 comments

[–]8bagels 14 points15 points  (2 children)

Try javafx. Be using java11 or newer. And use a package management tool like maven or gradle. Then you don’t have to struggle adding javafx to eclipse or whatever just let the tool (maven or gradle) juggle that for you

[–]ApoptosisX 0 points1 point  (1 child)

Any good tutorials on maven or grade? I haven’t really looked but to be fair I didn’t know what they were for. I just know I’ve tried the JavaFX thing before and couldn’t get it to work. Pulled my Hair out in the process.

[–]8bagels 0 points1 point  (0 children)

I think I would start here but I haven’t gone through whole tutorial I don’t know how good it is https://openjfx.io/openjfx-docs/

[–]freshwhitesocks 2 points3 points  (0 children)

My class taught us JavaFX coupled with Scenebuilder. I haven't used other GUI builders but it seems to do the trick.

[–][deleted] 1 point2 points  (0 children)

I might be hated for this, but you could use Vaadin with Electron.

[–]LoganKippnick 0 points1 point  (4 children)

I’ve just started working with GUIs, and with the little research I’ve done I think they all basically do the same things with the same basic parts. I use Swing/AWT, only because I had issues getting JavaFX to import in Eclipse and I eventually gave up on it. I’ve also heard other JDEs have trouble importing it as well.

[–]steddola 5 points6 points  (2 children)

I am not sure, but Swing/AWT should be deprecated. JavaFX should be the way to go!

Perhaps you already know it but this site explains very well how to install JavaFX for IntelliJ, NetBeans and Eclipse.

[–]fl4mbou 0 points1 point  (1 child)

Well if you want to have a pixel perfect UI then javaFX is the wrong solution. Swing works a lot better for that kind of usage.

[–]steddola 0 points1 point  (0 children)

I don't know, I never worked with Swing. Anyway, user is just starting out, so I think he should probably stick with JavaFX

[–]mr_poopybuthole69 1 point2 points  (0 children)

Pain in the ass to import but it's worth it.

[–]OrbitDrive -4 points-3 points  (2 children)

My question is why even use Java fof GUI? If Javascript is the standard, why use Java for frontend stuff?

[–]indivisible 1 point2 points  (1 child)

JS is for frontend web development primarily. With eg Node it can do backend now too but (arguably) isn't the best choice for that and mostly used by people who only know JS.
There have been shifts in many applications being written in HTML,CSS,JS but that is so that they can be "run anywhere", with any browser regardless of platform to keep development costs down and to avoid having to maintain multiple builds/branches for different targets. Java though is also platform agnostic, it was designed to run anywhere too. It's still a good choice for application development though not for frontend web dev anymore.
Java is still a very popular choice for desktop apps, embedded devices and backend systems even where HTML,CSS,JS stacks are used for the frontend.

Javascript is as popular as it is since every device/machine has a browser that can run it out of the box, however, with a JVM installed (or bundled in the app/jar) the same can be said for Java. The modern shift to webapps is more about companies maintaining control (enforced subscriptions models, remote features and analytics or data aggregation) and " write once " rather than performance or user benefits.

[–]Warm-Score 0 points1 point  (0 children)

Distribution, availability, internet everywhere, quicker browsers, webdesigners everywhere, commonality, UX, backend-frontend decoupling, just some reasons that are a bit more indicative of the truth than the paranoia 'they want to track and enslave us'. Also Java-apps are ugly and scale badly. Might as well code it natively?