Recent changes to Create a Controller

Create a Controller modified by Ralph

Ralph — Mon, 07 Mar 2016 07:18:04 -0000

--- v5
+++ v6
@@ -16,9 +16,7 @@
   @FXML
   private TableView<V> personTableView;
   @FXML
-  private TableColumn<V, String=""> person;
-  @FXML
-  private TableColumn<V, String=""> id;
+  private TableColumn<V, String=""> search;

   @Override
   public void initialize(URL location, ResourceBundle resources) {
@@ -28,9 +26,9 @@
 }
 ~~~~

-That is all to display the attribute *person* to the table view. The rest is done by fxDB.
+That is all to display the attribute *search* to the table view. The rest is done by fxDB.

-One thing is missing. How does the controller know how to match columns and attributes?
+One thing is missing. How does the controller know how to match entity columns and view object attributes?

 Please notice the generics: *V extends VoPerson*. Here the controller is informed about the type of the view object. For each column in the table view the controller will try to find the matching ...Property- method in the view object. This is the reason why we have implemented the annotated ...Property- methods in the view object.

Create a Controller modified by Ralph

Ralph — Wed, 24 Feb 2016 06:31:41 -0000

--- v4
+++ v5
@@ -32,7 +32,7 @@

 One thing is missing. How does the controller know how to match columns and attributes?

-Please notice the generics: *V extends VoPerson*. Here the controller is informed about the type of the view object. For each column in the table view the controller will try to find the matching get-Property- Method in the view object. This is the reason why we have implemented the annotated get-Property- Methods in the view object.
+Please notice the generics: *V extends VoPerson*. Here the controller is informed about the type of the view object. For each column in the table view the controller will try to find the matching ...Property- method in the view object. This is the reason why we have implemented the annotated ...Property- methods in the view object.

 And how does the controller known what query result set shall be displayed?

Create a Controller modified by Ralph

Ralph — Thu, 11 Feb 2016 17:11:16 -0000

--- v3
+++ v4
@@ -7,30 +7,32 @@
 Here we implement the view controller.

 ~~~~
-package com.tcs.contract;
+package de.hoppe.extra.person;

-public class ContractListController<V extends="" VoTransportAgreement=""> 
-      extends de.hoppe.fxDb.controller.DbListController<V>
-      implements Initializable {
+import ...

-   @FXML
-   private TableView<V> myTableView;
-   @FXML
-   private TableColumn<V, String=""> buNameCar;
+public class PersonListController<V extends="" VoPerson=""> extends DbListController<V> implements Initializable {

-   @FXML
-   @Override
-   public void initialize(URL location, ResourceBundle resource) {
-       setTableView(myTableView);
-   }
+  @FXML
+  private TableView<V> personTableView;
+  @FXML
+  private TableColumn<V, String=""> person;
+  @FXML
+  private TableColumn<V, String=""> id;
+
+  @Override
+  public void initialize(URL location, ResourceBundle resources) {
+    setTableView(personTableView);
+  }
+  ....
 }
 ~~~~

-That is all to display the attribute buNameCar to the table view. The rest is done by the fxDB.
+That is all to display the attribute *person* to the table view. The rest is done by fxDB.

-One thing is missing. How does the controller known how to match columns and attributes?
+One thing is missing. How does the controller know how to match columns and attributes?

-Please notice the generics: *V extends VoTransportAgreement*. Here the controller is informed about the type of the view object. For each column in the table view the controller will try to find the matching get-Property- Method in the view object. This is the reason why we have implemented the annotated get-Property- Methods in the view object.
+Please notice the generics: *V extends VoPerson*. Here the controller is informed about the type of the view object. For each column in the table view the controller will try to find the matching get-Property- Method in the view object. This is the reason why we have implemented the annotated get-Property- Methods in the view object.

 And how does the controller known what query result set shall be displayed?

Create a Controller modified by Ralph

Ralph — Fri, 05 Feb 2016 14:59:14 -0000

--- v2
+++ v3
@@ -1,11 +1,10 @@
 The controller is the missing link between a view object and a JavaFX stage.

 By using @FXML annotations each FX control can be injected into the controller.
-The controller has to know what view object shall be maintained.
+The controller has to know how a view object shall be maintained.
 Then it is easy for the controller to map attributes from the view object to the controls of the JavaFX stage.

-Now we implement the Controller.
-
+Here we implement the view controller.

 ~~~~
 package com.tcs.contract;

Create a Controller modified by Ralph

Ralph — Fri, 05 Feb 2016 12:18:56 -0000

--- v1
+++ v2
@@ -1,6 +1,6 @@
 The controller is the missing link between a view object and a JavaFX stage.

-By using @FXML annotations each control can be injected into the controller.
+By using @FXML annotations each FX control can be injected into the controller.
 The controller has to know what view object shall be maintained.
 Then it is easy for the controller to map attributes from the view object to the controls of the JavaFX stage.

@@ -28,3 +28,11 @@
 ~~~~

 That is all to display the attribute buNameCar to the table view. The rest is done by the fxDB.
+
+One thing is missing. How does the controller known how to match columns and attributes?
+
+Please notice the generics: *V extends VoTransportAgreement*. Here the controller is informed about the type of the view object. For each column in the table view the controller will try to find the matching get-Property- Method in the view object. This is the reason why we have implemented the annotated get-Property- Methods in the view object.
+
+And how does the controller known what query result set shall be displayed?
+
+[Create a Query Service] is the contents of the next page.

Create a Controller modified by Ralph

Ralph — Fri, 05 Feb 2016 12:07:07 -0000

The controller is the missing link between a view object and a JavaFX stage.

By using @FXML annotations each control can be injected into the controller.
The controller has to know what view object shall be maintained.
Then it is easy for the controller to map attributes from the view object to the controls of the JavaFX stage.

Now we implement the Controller.

package com.tcs.contract;

public class ContractListController<V extends VoTransportAgreement> 
      extends de.hoppe.fxDb.controller.DbListController<V>
      implements Initializable {

    @FXML
    private TableView<V> myTableView;
    @FXML
    private TableColumn<V, String> buNameCar;

    @FXML
    @Override
    public void initialize(URL location, ResourceBundle resource) {
        setTableView(myTableView);
    }
}

That is all to display the attribute buNameCar to the table view. The rest is done by the fxDB.