Creating the JavaFX converter was an interesting challenge and we will continue to refine the PDF to JavaFx conversion. My next challenge is to add the FXML version. I want to do this for several reasons:-
1. Increases the functionality of the conversion and offers alternatives.
2. It gets around the maximum file size issue in Java.
3. It looks like a really interesting technology!
JavaFXML is quite different in structure. Upon creating a new FXML project, three files are automatically created as opposed to the one file created when creating a java file or a JavaFX file.
– The first file contains the main method which makes the program runnable.
– The second file contains the xml equivalent of all the JavaFX commands. For example
<Button id="button" layoutX="126" layoutY="90" text="Click Me!" onAction="#handleButtonAction" fx:id="button" />
As opposed to
Button button = new Button();
– And the third file acts as an action listener as it has all the actions within it waiting to be executed depending on whether it is called up on.
Below is a diagram of my current understanding of the code, maybe you can correct me if am wrong?
During my quest to create a FXML converter, I will be sure to document/blog any interesting points I come across. Stay tuned…