Kbase 15100: ADM methodology and SHARED structure definitions
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
ADM methodology and SHARED structure definitions
The ADM (Application Development Model) provides a standard
architecture and programming approach for building and reusing program
objects. Via the UIB, it also provides a programming interface
that can be used to design the object templates and assemble the
programs that access them. This design paradigm allows objects
to be reused again and again, with changes to an object's main source
file propogating automatically through all instances of it within an
application.
By definition, these objects are encapsulated. This means that all
information about the object and its actions are contained within it.
This allows other objects to interact with it by asking it to perform
its associated task.
The requirement that objects be encapsulated means that it is not
recommended that SHARED structures such as shared buffers, variables,
temp-tables, etc. be used. A shared structure negates object
encapsulation by making the object dependent on a definition and/or
initialization outside of itself.
Rather than shared structures, an ADM object should make use of input
and output parameters.
Previously-written programs that make use of shared data structures
will need to be redesigned if they are to be fit into the ADM.
Programmers who do not wish to use the ADM can still design programs
in the UIB simply by using the basic widget set that existed in
the Version 7 UIB. When using the basic UIB, shared structures can
be used freely.
Progress Software Technical Support Note # 15100