Trace:
Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
jvx:firstapp [2018/01/25 08:12] admin |
jvx:firstapp [2018/01/25 08:32] admin |
||
---|---|---|---|
Line 138: | Line 138: | ||
^ Method ^ Description ^ | ^ Method ^ Description ^ | ||
- | | Constructor | A specific constructor is needed, as each application is started with a launcher which depends on the technology used. This launcher is passed over to the application in the constructor. | | + | |Constructor|A specific constructor is needed, as each application is started with a launcher which depends on the technology used. This launcher is passed over to the application in the constructor.| |
- | |createConnection|The communication protocol is initialised. A DirectServerConnection is sufficient for our application, as both the client and the server are started in the same VM. However, if an application server is integrated, a HttpConnection could also be used.| | + | |createConnection|The communication protocol is initialised. A ''DirectServerConnection'' is sufficient for our application, as both the client and the server are started in the same VM. However, if an application server is integrated, a ''HttpConnection'' could also be used.| |
- | |getApplicationName|Sets the application name. This name is needed for the communication with the server, as the latter uses the appropriate application configuration depending on the application name. In our case, the application name must be firstapp as the working directory is also called ../JVxFirstApp/rad/firstapp/.| | + | |getApplicationName|Sets the application name. This name is needed for the communication with the server, as the latter uses the appropriate application configuration depending on the application name. In our case, the application name must be firstapp as the working directory is also called ''../JVxFirstApp/rad/**firstapp**/''.| |
|afterLogin|This method is called by the super class after a successful login. We use this method to extend our menu and our toolbar.\\ \\ It is not necessary to reset the changes after logout, as this is done automatically by the super class.| | |afterLogin|This method is called by the super class after a successful login. We use this method to extend our menu and our toolbar.\\ \\ It is not necessary to reset the changes after logout, as this is done automatically by the super class.| | ||
|createMenuItem|Provided by the super class to create menu entries. The first parameter contains the name of the method which is to be called when the menu entry is selected. The second parameter contains the command (ActionCommand) which plays no role in our case. The text of the menu entry is to be defined in the third parameter, and lastly the image for the entry is passed over.| | |createMenuItem|Provided by the super class to create menu entries. The first parameter contains the name of the method which is to be called when the menu entry is selected. The second parameter contains the command (ActionCommand) which plays no role in our case. The text of the menu entry is to be defined in the third parameter, and lastly the image for the entry is passed over.| | ||
- | |createToolBarButton|Similar to createMenuItem, except that this method creates a button which adapts to the layout of the toolbar.| | + | |createToolBarButton|Similar to ''createMenuItem'', except that this method creates a button which adapts to the layout of the toolbar.| |
|UIImage.getImage|Provides a predefined image from the JVx image library. For ease of use, we use a predefined image.| | |UIImage.getImage|Provides a predefined image from the JVx image library. For ease of use, we use a predefined image.| | ||
|doOpenDBEdit|This method is called when the menu or the toolbar button are pressed and calls the corresponding work screen.| | |doOpenDBEdit|This method is called when the menu or the toolbar button are pressed and calls the corresponding work screen.| | ||
Line 258: | Line 258: | ||
} // DBEditFrame | } // DBEditFrame | ||
</file> | </file> | ||
+ | |||
+ | ^ Method ^ Description ^ | ||
+ | |initializeModel|Initialises the client objects for the access to the server or the data.| | ||
+ | |InitializeUI|Layouting of the work screen.| | ||
+ | |createSubConnection|We create a separate connection to the server. This has the advantage that a separate business object is used on the server. This object contains all objects needed by the work screen. Once the work screen is closed, the used memory is released. Moreover, each connection can have special parameters and time outs. \\ The requested business object is defined with the following class: ''apps.firstapp.frames.DBEdit''. \\ \\ The class will be created later on.| |