Progress
Language Tutorial
for Windows
Summary
Event-driven programs strive to make as much functionality available from the top-level of an application as possible. This leads to a characteristic flat application structure consisting of one large main procedure and several atomic modules that reside in separate procedure files. Having a large main procedure may tax the execution limits of your system. To alleviate this problem, you can use persistent procedures to create loadable and unloadable modules of resources.
SHARED resources, including variables, frames, buffers, queries, and streams, allow you to create individual resources that can be available to many procedures.
Persistent procedures create resources that do not disappear when the creating procedure ends. Persistent procedure contexts must be destroyed programmatically when the application no longer needs them.
Progress supports a variety of interface designs, including:
Like other widgets, frames and windows have attributes that you can manipulate to fine tune your interface.
A successful application that mingles more than one interface needs to manage application control by using WAIT-FOR statements, implied application blocking, and persistent procedures in such a way as to give the user freedom to move through the application without conflict.
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |