Documentation

Trace:

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
jvx:reference [2019/02/26 11:03]
admin [Creating the Implementation]
jvx:reference [2019/02/27 23:06] (current)
robot
Line 2: Line 2:
  
 ~~Title: JVx Concepts and Reference~~ ~~Title: JVx Concepts and Reference~~
-Version: 1.0 / 2018-05-22+Version: 1.0 / 2019-02-27
  
 ====== Introduction ====== ====== Introduction ======
Line 827: Line 827:
 Of course [[https://​sourceforge.net/​projects/​jvx/​|JVx]] wouldn’t be that useful if it would just provide static GUI components. Now, to explain what else is required for a remote [[https://​sourceforge.net/​projects/​jvx/​|JVx]] application I have to go far afield, so let’s head down the rabbit hole. Of course [[https://​sourceforge.net/​projects/​jvx/​|JVx]] wouldn’t be that useful if it would just provide static GUI components. Now, to explain what else is required for a remote [[https://​sourceforge.net/​projects/​jvx/​|JVx]] application I have to go far afield, so let’s head down the rabbit hole.
  
-{{:​jvx:​reference:​jvx-client-server.png?​nolink|JVx Layers}}+{{:​jvx:​reference:​jvx-client-server.png?​nolink| Layers}}
  
 What you are seeing here is a rough sketch of how the architecture of [[https://​sourceforge.net/​projects/​jvx/​|JVx]] looks like. Let’s walk through the image step by step. We will look at each successive layer and work our way from the database on the server to the databook on the client. What you are seeing here is a rough sketch of how the architecture of [[https://​sourceforge.net/​projects/​jvx/​|JVx]] looks like. Let’s walk through the image step by step. We will look at each successive layer and work our way from the database on the server to the databook on the client.
Line 1194: Line 1194:
 If we take a good look at the CellEditorHandler interface, we see that it contains everything that is required for setting up a component to be able to edit data coming from a DataRow. One method is especially important, the ''​%%getCellEditorComponent()%%''​ function. It returns the actual technology component that is to be embedded into the Editor. That means that even though there are implementations for the CellEditors on the UI layer, the actual components which will provide the functionality for editing the data are implemented on the technology layer. A short refresher: If we take a good look at the CellEditorHandler interface, we see that it contains everything that is required for setting up a component to be able to edit data coming from a DataRow. One method is especially important, the ''​%%getCellEditorComponent()%%''​ function. It returns the actual technology component that is to be embedded into the Editor. That means that even though there are implementations for the CellEditors on the UI layer, the actual components which will provide the functionality for editing the data are implemented on the technology layer. A short refresher:
  
-{{:​jvx:​reference:​layers.png?​nolink|The different layers of JVx, User, UI Wrappers, Implementations,​ Extensions and the Technology.}}+{{:​jvx:​reference:​layers.png?​nolink|The different layers of , User, UI Wrappers, Implementations,​ Extensions and the Technology.}}
  
 Revisiting our simple screen from above, we’d actually need to represent it as something like this: Revisiting our simple screen from above, we’d actually need to represent it as something like this:
Line 1389: Line 1389:
  
 <code java> <code java>
-public class SwingProgressBar<​ExtendedProgressBar> ​extends SwingComponent +public class SwingProgressBar extends SwingComponent 
-                                                   ​implements IProgressBar+                              implements IProgressBar
 { {
     public SwingProgressBar()     public SwingProgressBar()
Line 1446: Line 1446:
  
 <code java> <code java>
-public class UIProgressBar<​IProgressBar> ​extends UIComponent<​IProgressBar>​ +public class UIProgressBar extends UIComponent<​IProgressBar>​ 
-                                         ​implements IProgressBar+                           ​implements IProgressBar
 { {
     public UIProgressBar()     public UIProgressBar()
This website uses cookies for visitor traffic analysis. By using the website, you agree with storing the cookies on your computer.More information