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:package_overview [2018/01/29 15:00]
admin
jvx:package_overview [2020/06/10 13:13] (current)
cduncan Edited for English grammar (capitalization, punctuation, correct verb conjugation)
Line 1: Line 1:
-~~Title: Package ​overview~~+~~Title: Package ​Overview~~
  
-The [[https://​jvx.sibvisions.com|JVx]] Enterprise Application Framework is a powerful tool for the creation of database applications. However, attention is always paid to simplicity and modularity. Therefore, JVx consists of several packages which can be used separately or in combination.+The [[https://​jvx.sibvisions.com|JVx]] Enterprise Application Framework is a powerful tool for the creation of database applications. However, attention is always paid to simplicity and modularity. Therefore, JVx consists of several packageswhich can be used separately or in combination.
  
 The following packages are components of JVx: The following packages are components of JVx:
Line 8: Line 8:
     * [[#​genui|Generic User Interface (Generic UI)]]     * [[#​genui|Generic User Interface (Generic UI)]]
     * [[#​swing|Swing]]     * [[#​swing|Swing]]
-    * other UI platforms+    * Other UI Platforms
   * [[#​model|Generic Model]]   * [[#​model|Generic Model]]
   * [[#​remote|Remote]]   * [[#​remote|Remote]]
Line 17: Line 17:
 == User Interface (UI) (javax.rad.ui) == == User Interface (UI) (javax.rad.ui) ==
  
-The JVx UI defines which possibilities the User Interface ​must offer so as to build an Enterprise ​application. These are based on minimal requirements so as not to create any extra ballast. Basically the UI consists of simple interfaces with which the necessary attributes are defined in a technology independent manner. The goal was to use the one application with various GUI technologies without even having to change a line of code.+The JVx UI defines which possibilities the user interface ​must offer in order to build an enterprise ​application. These are based on minimal requirements so as not to create any extra ballast. Basicallythe UI consists of simple interfaces with which the necessary attributes are defined in a technology-independent manner. The goal was to use the one application with various GUI technologies without even having to change a line of code.
  
 {{anchor:​genui:​}} {{anchor:​genui:​}}
 == Generic User Interface (Generic UI)  (javax.rad.genui) == == Generic User Interface (Generic UI)  (javax.rad.genui) ==
  
-The generic UI is a technology-independent implementation of the UI. It consists of concrete classes which act as wrappers for the preferred ​technologie. Thanks to the generic UI, it is possible to reach a high level of comfort when developingbecause it is easily possible to derive one's own classes and integrate them into applications. Only with interfacesthis would not be possible.+The generic UI is a technology-independent implementation of the UI. It consists of concrete classes which act as wrappers for the preferred ​technology. Thanks to the generic UI, it is possible to reach a high level of comfort when developing because it is easily possible to derive one's own classes and integrate them into applications. Only with interfaces ​is this not possible.
  
 {{anchor:​swing:​}} {{anchor:​swing:​}}
 == Swing (com.sibvisions.ui.swing) ==  == Swing (com.sibvisions.ui.swing) == 
  
-The Swing package contains the technology-independent UI implementation for Swing. On the one hand, standard Swing components were used, on the other extended Swing components were implemented. The extended components offer extra functionality and can also be used seperately ​with other Swing-based applications.+The Swing package contains the technology-independent UI implementation for Swing. On the one hand, standard Swing components were used, on the otherextended Swing components were implemented. The extended components offer extra functionality and can also be used separately ​with other Swing-based applications.
  
 {{anchor:​model:​}} {{anchor:​model:​}}
 == Dynamic Model (javax.rad.model,​ com.sibvisions.rad.model) ==  == Dynamic Model (javax.rad.model,​ com.sibvisions.rad.model) == 
  
-The dynamic model defines an active model for usage in the UI. This is in principle several interfaces with which the attributes of the model are described. All UI controls use these interfaces to display and manipulate data. The model has already been implemented for the use of data in the main memory and for the access to databases. The actual database access takes place thanks to the Remote package.+The dynamic model defines an active model for usage in the UI. This isin principleseveral interfaces with which the attributes of the model are described. All UI controls use these interfaces to display and manipulate data. The model has already been implemented for the use of data in the main memory and for the access to databases. The actual database access takes place thanks to the Remote package.
  
 {{anchor:​remote:​}} {{anchor:​remote:​}}
 == Remote (javax.rad.remote,​ com.sibvisions.rad.remote) == == Remote (javax.rad.remote,​ com.sibvisions.rad.remote) ==
  
-In the remote package, the protocol-independant ​communication between client and server is, on the one hand, defined, and on the other hand, its use with Master- and SubConnection is implemented. Each communication between client and server is executed with this package. The communication via HTTP(S) has already been fully implemented.+In the remote package, the protocol-independent ​communication between client and server is, on the one hand, defined, and on the other hand, its use with Master- and SubConnection is implemented. Each communication between client and server is executed with this package. The communication via HTTP(S) has already been fully implemented.
  
 {{anchor:​server:​}} {{anchor:​server:​}}
 == Server (javax.rad.server,​ com.sibvisions.rad.server) == == Server (javax.rad.server,​ com.sibvisions.rad.server) ==
  
-The Server package defines the attributes of a server ​which is fully supported by Jvx and the communication package (Remote). This definition covers the communication possibilities,​ a Master-/​SubSession administration and the lifecycle management. The communication via HTTP(S) has already been fully implemented.+The Server package defines the attributes of a server ​that is fully supported by Jvx and the communication package (Remote). This definition covers the communication possibilities,​ a Master-/​SubSession administrationand the lifecycle management. The communication via HTTP(S) has already been fully implemented.
  
 {{anchor:​persist:​}} {{anchor:​persist:​}}
This website uses cookies for visitor traffic analysis. By using the website, you agree with storing the cookies on your computer.More information