A JavaFX application exists and the application is starting from the Main.class file which extends Application:
public class Main extends Application { /** * Keep a reference to the main Stage */ public static Stage stage; /** * MainScene Controller */ public static MainScene mainSceneController; /** * The Capture Window of the application */ public static CaptureWindow captureWindowController; /** * Settings Scene Controller */ public static SettingsController settingsController; @Override public void start(Stage primary) throws Exception { stage = primary; .......... // CaptureWindow FXMLLoader loader1 = new FXMLLoader(getClass().getResource("/fxml/CaptureWindow.fxml")); loader1.load(); captureWindowController = loader1.getController(); // MainScene mainSceneController = new MainScene(); ......... } }
Description
As you can see above I have 3 FXMLControllers(one is reusable[extends StackPane],others not).I have declared all of them static cause i want to access variables from one FXMLController from the other FXMLControllers.I use this strategy every time I use JavaFX and I don't think is good...
How I can change the code below so I can access variables or methods of one FXMLController from other FXMLController? Is that possible without using static keyword?
Consider that the Controllers are represented from different classes which can be in different packages.
Actually the answer for this question seems a little bit complicated it has to do with MVC pattern and it's evolution until now.We will use MVP Pattern.
After a long discussion i got a link on this website http://martinfowler.com/eaaDev/uiArchs.html defining the historical evolution of the different patterns used from the old ages of Smalltalk until now.
The actually solution is using Model Viewer Presenter Pattern(MVP) which can be visually described using these images:
Last but not least have a look at the comments here:
Finally:
If anything is inaccurate feel free to edit.
回答2:
I think you are not supposed to declare @FXML annotated attributes with the static keyword. See this GitHub project on how you should do it. Like that you instantiate a controller only when it is needed, and your app will be stateless.
回答3:
JavaFx is mostly composed of set of [well designed] tools but unfortunately by itself does not provide a good framework for creating complex UI designs e.g. MVC/MVP patterns, view flows and actions on multiple controllers, So you have to rely on third-party application frameworks for those for example:
In my opinion none of them are widely used or mature enough to be considered a de facto standard but using them is encouraged.
Example Using DataFx
DataFx uses a concept named Flow to associate views sharing a flow of events (and possibly data) among themselves. By using Flow combined with EventSystem you can define and access methods on other controllers and assign custom event listeners to various events associated with JavaFx Nodes in different controllers sharing a flow.
Here is an example from DataFx samples which represents two separate sender and receiver views with distinct FXML files and controllers:
public class EventSystemDemo extends Application { @Override public void start(Stage primaryStage) throws Exception { HBox box = new HBox(); box.setSpacing(12); box.setPadding(new Insets(12)); box.setFillHeight(true); box.setAlignment(Pos.CENTER); Flow senderFlow = new Flow(ProducerController.class); box.getChildren().add(senderFlow.start()); Flow receiverFlow = new Flow(ReceiverController.class); box.getChildren().add(receiverFlow.start()); primaryStage.setScene(new Scene(box)); primaryStage.show(); } public static void main(String... args) { launch(args); } }
You can implement your own controller factory so you would be able of creating your own controllers context.
I have used spring with javaFX, and I have implemented my own controllers factory using spring, in that way you can inject one controller in other (you shouldn't need it as those connections should be on the model)
