Trace:
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
jvx:firstapp_step-by-step [2018/01/30 10:31] admin |
jvx:firstapp_step-by-step [2018/01/30 11:49] admin |
||
|---|---|---|---|
| Line 174: | Line 174: | ||
| ^Method^Description^ | ^Method^Description^ | ||
| |Constructor|The standard constructor cannot be used, as each application is started with a technology-dependent launcher. This launcher is already passed to the application in the constructor.| | |Constructor|The standard constructor cannot be used, as each application is started with a technology-dependent launcher. This launcher is already passed to the application in the constructor.| | ||
| - | |createConnection|The communication protocol is initialised. A DirectServerConnection is sufficient for our application, because both the client and the server are started in the same VM. However, if an application server is in use, a HttpConnection could also be used.| | + | |createConnection|The communication protocol is initialised. A ''DirectServerConnection'' is sufficient for our application, because both the client and the server are started in the same VM. However, if an application server is in use, 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, because the work directory is also called ''../JVxFirstApp/rad/firstapp/''. The application name MUST always match the directory name!| | + | |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'', because the work directory is also called ''../JVxFirstApp/rad/**firstapp**/''. The application name MUST always match the directory name!| |
| It is now time for the first start of the application. To do so, we set up a Runtime configuration: | It is now time for the first start of the application. To do so, we set up a Runtime configuration: | ||
| Line 207: | Line 207: | ||
| </file> | </file> | ||
| - | Any number of user lines can be entered! | + | Any number of ''user'' lines can be entered! |
| Now the login to the application works perfectly. However, to fulfill our task, we still need the possibility to display or edit a database table. We will now turn to this part of the task. | Now the login to the application works perfectly. However, to fulfill our task, we still need the possibility to display or edit a database table. We will now turn to this part of the task. | ||
| Line 505: | Line 505: | ||
| ^Method^Description^ | ^Method^Description^ | ||
| - | |doOpenDBEdit|The method can easily throw a Throwable. All application errors are caught by the application and shown in an information dialogue.| | + | |doOpenDBEdit|The method can easily throw a ''Throwable''. All application errors are caught by the application and shown in an information dialogue.| |
| |configureFrame|This method is provided by the super class and ensures that all frames have a similar look. This also includes the menu icon.| | |configureFrame|This method is provided by the super class and ensures that all frames have a similar look. This also includes the menu icon.| | ||
| Line 634: | Line 634: | ||
| ^Description^ | ^Description^ | ||
| - | |The class represents the lifecycle object for the DBEditFrame work screen. The objects can only be accessed via the SubConnection of the work screen. \\ \\ Thanks to the inheritance of ''apps.firstapp.Session'' it is very easy to access all Session and Application objects.| | + | |The class represents the lifecycle object for the ''DBEditFrame'' work screen. The objects can only be accessed via the SubConnection of the work screen. \\ \\ Thanks to the inheritance of ''apps.firstapp.Session'' it is very easy to access all ''Session'' and ''Application'' objects.| |
| ^Method^Description^ | ^Method^Description^ | ||