| Disappointed in e(fx)clipse (and Eclipse. [message #1755181]
||Tue, 28 February 2017 17:36
| Jan Stes
Registered: February 2017
new to java et al. Trying to learn java, javaFX, FXML and SceneBuider.|
Started with NetBeans as IDE. Works fine. Saw on some YouTube video's that eclipse seemed to have the better editor. Decided to switch.
Installation of Eclipse Neon.2 was OK. Then found out that std Eclipse does not support FXML projects .
Had to find and install e(fx)clipse. Not easy, Info on the web very confusing. Ended up with installation from "best solutions". But that was NOT the best solution (older version of eclipse Neon). Had to revert back to blank install and install an "update" for e(fx)clipse. Looked OK, but after a while more searching the web, found that this was not the latest version of e(fx)clipse.. To get the current production version you have to install from the nightly build site... However the info about that is well hidden.
Furthermore, none of the sites around e(fx)clipse are up to date, and they certainly are not congruent. I am truly disappointed in eclipse foundation that they accept such a shambles in one of their projects.
It took me an 10 hour day to work through this. And I still would not have written this entry, if it all worked out in the end.
But it has not worked out at all !!!!!!!
e(f*$à9)clipse does not support re-generation/update of the FMXL controller that you need. It only provides a (template) generation. Which means that the real FMXL-Code integration has to be coded by hand and integrated in that controller each time the GUI changes. That renders, in my view, eclipse totally useless for use with javaFX, FXML and SceneBuider.
AND NETBEANS DOES THIS PERFECTLY!!!!!!!
I'm going back to NetBeans, despite the slightly more cumbersome editor.
Powered by FUDForum
. Page generated in 0.01709 seconds