Kbase P25820: Dynamics. Benefits of the Repository.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
26/05/2003 |
|
Status: Unverified
GOAL:
Dynamics. Benefits of the Repository.
FACT(s) (Environment):
Dynamics 2.0A
FIX:
Benefits of the Repository
The Dynamics Object Repository stores data for a wide variety of purposes. Most application objects are represented as data stored in the repository, so that you don·t need to create, compile, deploy, and maintain source code for them. A dynamic window can contain a dynamic Toolbar instance, a dynamic Browser to display multiple records from a query, and a dynamic Viewer to display and allow update of fields from a single record. These objects are represented as data in repository tables, and realized at runtime by a handful of procedures that know how to create any object of their type: window, toolbar, browser, or viewer.
Managing an application in this way greatly reduces the amount of Progress 4GL code in the application, resulting in a smaller application footprint, therefore less r-code to deploy to client work stations where the application will be run. It also provides much greater flexibility in the maintenance of the application, and in the ways in which you can use it. A change to a single driver procedure can change the way an entire aspect of an application looks or behaves without the need to modify or even recompile large numbers of existing procedures. And an abstract, repository-based definition of the application supports its deployment to a variety of client platforms.