'jFormTK' Databases

The 'jFormTK' Package establishes the following 'jFormTK' Databases designed to control 'jFormTK' System and Application control parameters.

Table of Contents…
The 'jFormTK' Database [JFormTKDB]
The Application Database [appDB]
The Application Common Database[AppCommonDB]
The Application Embedded Database [Derby / JavaDB]

'jFormTK' Database [JFormTKDB]

This database is a collection of elements designed to control the 'jFormTK' System Parameters . It contains the parameters designed to control the 'jFormTK' Application Look and Feel.

The 'jFormTK' Database Look and Feel parameters uses the 'jFormTK.JLAF' class [ see ] exclusively to produce a components Look and Feel. The 'JLAF' class has the following control parameters:

For example, the default Look and Feel parameters for the TabPanel, Form Panel, Show Panel, Address Book Panel, Button Panel, Status Display, Table Edit Panel, Dynamic Referencing Popup, Help Panel, Hint Panel, etc. are contained in this database.
Most of this database parameters are built from the following 'jFormTK' Application "Primitive" controls of this 'JFormTKDB' Database:

The above "Primitive" controls may be used to "customize" the entire Look and Feel for the 'jFormTK' Application. For example, the Professional Computer Solutions Survivors List PLUS 'jFormTK' Application uses a shade of brown for the 'appBackground' color and a shade of tan for the 'appForeground' color. If PCS is successful at licensing custom Survivors List PLUS Application, these and other 'JFormTKDB' Database elements shall be changed to match the licensee's company colors and Logo.

NOTES:
1) The 'jFormTK' Application specific controls are defined by "Over Loading" the 'jFormTK.Main.loadJFormTKDB_Ordered_Pairs' Method in the 'jFormTK.Main' subclass. [ see ]


2) This JFormTKDB Database is a "Static" Database. It is built from the 'jFormTK Kernel' baseline Database and adjusted for the specific application requirements during the "Install Phase". It may not be changed during the application execution phase.


CONTROLS…
TOP
TOC
Return to Overview TOC


The Application Database [AppDB]

The 'AppDB' database contains the Application peculiar parameters, i.e. the parameters that the jFormTK' kernel uses to uniquely identify the 'jFormTK' Application. This database also contains elements to identify the company responsible for the development and distribution of this specific 'jFormTK' Application. In addition, this database is host to "Version Control" parameters, e.g. the "Copyright" year and the Application version number. Examples of some of the parameters in this database are as follows:

NOTES:
1) Roots are the file directory / folder information where the 'jFormTK' Application files shall be stored.


2) The AppDB Database "Over Loading" the 'jFormTK.Main.loadAppDB_Ordered_Pairs' Method in the 'jFormTK.Main' subclass. [ see ]


3) This AppDB Database is a "Static" Database. It is built from the 'jFormTK Kernel' baseline Database and adjusted for the specific application requirements during the "Install Phase". It may not be changed during the application execution phase.


CONTROLS…
TOP
TOC
Return to Overview TOC


The Application Common Database[AppCommonDB]

This 'jFormTK' database is designed to contain sets of "Ordered Pairs" that may be set and used in "run-time". This database is a Dynamic database and contains "Persistent" data elements that are available to the current 'jFormTK' run-time execution and to subsequent 'jFormTK executions.

"Ordered Pairs" are database elements that contain the following values:
  1. 'Key' - The element Name.
  2. 'Value' - The element value associated to the above 'Key'.
Example "Ordered Pairs" : ("UserNickname", "Jim")

NOTE:
"Persistent Data" Definition:
Persistent data is data that exists from session to session. Persistent data is stored in a database so that it may be reloaded when an application is re-executed. In data entry programs, such as a 'jFormTK' application, the data is written to a re-loadable database as it is entered into a form field. These "Persistent Data" application do not have a "Save" button because the data is always written to a re-loadable database.


CONTROLS…
TOP
TOC
Return to Overview TOC

The Application Embedded Database [Derby / JavaDB]

The 'jFormTK' kernel uses the Derby database to save it's data entry values as they are entered by the application end user. Derby is an embedded relational Database with an SQL interface. It is the "Heart" of the 'jFormTK' Kernel. It contains a database table for each application form and a database table for the run-time 'jFormTK  controls.

The Derby embedded database is fundamental in maintaing the "Persistent Data" for all data entry form values and the maintenance of the "Dynamic" 'AppCommonDB'.

NOTE:
Starting with Java version 1.6 the Derby Database is contained in the Java distribution. In that Java environment, the Derby Database is references as the JavaDB.


CONTROLS…
TOP
TOC
Return to Overview TOC