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:features [2020/06/08 12:57] cduncan [Quick & Easy development] |
jvx:features [2020/06/08 12:58] cduncan [How does it work?] |
||
|---|---|---|---|
| Line 91: | Line 91: | ||
| </WRAP> | </WRAP> | ||
| - | ===== How does it work? ===== | + | ===== How Does It Work? ===== |
| <WRAP group> | <WRAP group> | ||
| Line 98: | Line 98: | ||
| </WRAP> | </WRAP> | ||
| <WRAP column third> | <WRAP column third> | ||
| - | //JVx' DAO class DBStorage analyzes the data model of table "CONTACTS". This detects all data types for all columns and all foreign keys to master data tables. This metadata information are sent to the client model. | + | //JVx' DAO class DBStorage analyzes the data model of table "CONTACTS". This detects all data types for all columns and all foreign keys to master data tables. This metadata information is sent to the client model. |
| \\ | \\ | ||
| \\ | \\ | ||
| The dynamic client model, for all Daten data-bound GUI controls, uses this metadata. | The dynamic client model, for all Daten data-bound GUI controls, uses this metadata. | ||
| - | Because of this mechanism, all input fields get a specific data type, and size directly from the database. Dropdown lists are created because of foreign key references to master data tables, etc. | + | Because of this mechanism, all input fields get a specific data type and size directly from the database. Dropdown lists are created because of foreign key references to master data tables, etc. |
| \\ | \\ | ||
| \\ | \\ | ||
| - | As a result, no further source code is necessary.\\ **Covention over Configuration** | + | As a result, no further source code is necessary.\\ **Covention Over Configuration** |
| \\ | \\ | ||
| Any deviation from the standard behavior can be coded accordingly. | Any deviation from the standard behavior can be coded accordingly. | ||