PCEngineFans.com - The PC Engine and TurboGrafx-16 Community Forum

Tech and Homebrew => Turbo/PCE Game/Tool Development => Topic started by: Bonknuts on August 19, 2016, 02:49:40 PM

Title: Making some of my pce dev tools public
Post by: Bonknuts on August 19, 2016, 02:49:40 PM
Since I'm taking another Java level course, I figure I might as well get in some practice. I've never really worked with gui frameworks before (all my stuff was hand build internal gui code). Jframe seems decent and I've learned to write some interfacing code for it.

 But here's my question; does it matter of the program is a JAR file or windows EXE file? I can wrap the JAR into an EXE launcher, but you'll still need to install Java SDK to run it.

 Also, anyone familiar with Jframe, or another gui framework for Java that they recommend?
Title: Re: Making some of my pce dev tools public
Post by: touko on August 20, 2016, 06:01:28 AM
Personaly, if it does the job i don't care . ;-)
It's already nice when someone post his public tools, exe or java it's really not that important .
Title: Re: Making some of my pce dev tools public
Post by: Arkhan on August 23, 2016, 02:15:06 PM
all Java UI libraries are bad, so just pick whichever.

Title: Re: Making some of my pce dev tools public
Post by: spenoza on August 23, 2016, 02:35:21 PM
When I was working in JAVA Swing was acceptable. These days it's probably considered decrepit.

Oh, thank you Google. Turns out JavaFX is the replacement.

Honestly, work in Swing or JavaFX. Swing is a foundation class and JavaFX and Swing are both included in JAVA at this point. Your tools should be functional and easy to use first, shiny and attractive second.
Title: Re: Making some of my pce dev tools public
Post by: NightWolve on August 23, 2016, 03:29:41 PM
My general preference was to wrap a JAR file in an EXE rather than having to keep batch files handy to launch it.
Title: Re: Making some of my pce dev tools public
Post by: Bonknuts on August 23, 2016, 07:34:34 PM
OK, cool. Thank all for chiming in. I think I'll probably wrap it in an EXE. Can't hurt, and somehow looks more "complete" to me for some reason (probably my old legacy perspectives).

 spenoza: JavaFX sounds familiar. I'll check that out.