This chapter explains how to add integration hooks to the Procedure Editor by describing the parameters and events for adecomm/_adeevnt.p and how to modify this procedure to interface with source code management or your own proprietary tools:
Source code management tools or your own proprietary tools can interface with the Procedure Editor. They can intercept and augment tool behavior at the following critical points in the application development process:
Opening, closing, and saving files
Before and after a file is run, debugged, or checked for syntax
Startup and shutdown of the Procedure Editor
To allow source code management or your own proprietary tools to “trap” these ADE events, the Procedure Editor calls a procedure file, adecomm/_adeevnt.p, at those critical processing points. You can modify this procedure to intercept and augment standard tool behavior. The source code to this procedure is provided by Progress Software Corporation. To use this procedure, you must copy the source code, modify it, compile it, and place it in your PROPATH.
Note: For GUI application development, there are three procedure files for integration hooks—adecomm/_adeevnt.p, adecomm/_getfile.p, and adecomm/_chosobj.w. For more information on how to use integration hooks for GUI application development, see the on-line help.
Opening, closing, and saving files