Amno, It is not a zero-sum choice. FXML is a part of JavaFX. FXML does not add anything, per se (in terms of nodes, controls, etc.) FXML allows for decoupling the specific UI configuration (in terms of what nodes contain which and their positions, etc.). Basically it is the most sustainable (in terms of increasing application size/scope) practice to use FXML for setting up the initial scenes (and perhaps also wiring event listeners)
In the Android world it is equivalent to using the Layout Editor (similar to FXML) versus making the scene programmatically by calling constructors, setting ownership, positions, constraints, etc. There is nothing that can be done using FXML that can't be done using pure Java. Cheers, Michael Ennen On Thu, Sep 6, 2018 at 4:48 PM AmnoJeeuw <amnoje...@gmail.com> wrote: > I am learning hands-on how to program using JavaFX and in the process > doing so I’ve come across FXML; which I find most interesting. Since the > principal is “Think hand held device first” -TH2DF, my intention is to > port the my future application to Android device, but I am concerned > that there will be too many issues when doing that. So, my question is, > which technology should give preference to, JavaFX or FXML? > > Please, keep in mind that I am using a Windows 8.1 machine and > Eclipse-Photon. > > > Thanks in advance > > -- > ArbolOne > Using Fire Fox and Thunderbird. > Developing using Java, C/C++, HTM/CSS and JS as our platform has been > exciting and most rewarding. > [ Sí ] > >
