Kenneh Posted September 29, 2013 Posted September 29, 2013 JavaFX does indeed look nicer than swing, but doesn't exactly perform faster. I'm glad you're going to organize the api, the current methodprovider class is a trainwreck (what the hell were you guys thinking? throwing all the methods into one class makes it really hard to find what you need). Also, hopefully in the re-write every interaction method wont throw an interrupted exception, it's annoying to deal with. If you plan on using JFX, you're going to have to release a custom jre with it because JFX won't ship with java til jre8(?). Oh yeah, and remove groovy, no one uses it. It just makes the jar obnoxiously large.
Wrecks Posted September 29, 2013 Posted September 29, 2013 Looks and sounds perfect, can't wait to try!
Developer Maxi Posted September 30, 2013 Author Developer Posted September 30, 2013 JavaFX does indeed look nicer than swing, but doesn't exactly perform faster. I'm glad you're going to organize the api, the current methodprovider class is a trainwreck (what the hell were you guys thinking? throwing all the methods into one class makes it really hard to find what you need). Also, hopefully in the re-write every interaction method wont throw an interrupted exception, it's annoying to deal with. If you plan on using JFX, you're going to have to release a custom jre with it because JFX won't ship with java til jre8(?). Oh yeah, and remove groovy, no one uses it. It just makes the jar obnoxiously large. It performs slightly faster when it comes to drawing as it uses a smaller time step in its engine than Swing. Swing uses a 5ms time step where as JavaFX allows for smaller time steps. We won't have to release a custom JRE, we will probably simply provide the JavaFX runtime through booting.
A lazy Cat Posted September 30, 2013 Posted September 30, 2013 So the main outcome of this will be more stable botting?
