In traditional (procedural) programming, the developer dictates the order in which events occur and when information is presented to the user. The user has minimal or no control over the program because the code is not attached to specific objects with which the user interacts.
However, in an event-driven program, users have greater control in directing the order in which events occur. In essence, the code for an event-driven program is written in small blocks that are attached to program objects. It is the user interaction with these objects or events that trigger code execution.
It is important that the developer have a firm understanding
of how event-driven programming differs from traditional programming.
However, fin-depth knowledge of these concepts is not necessary
to implement ODL effectively.
Copyright © 2005. Sybase Inc. All rights reserved. |
![]() |