Whitepapers, discussions, and code related to tools for programming in ABL, analyzing existing code, and improving and transforming ABL code.
If you are using "ED for Windows" (version 4) and are editing .p or .w files, you can use this tool as a communication bridge between ED for Windows and a Progress session.
You can do:
- create a "Compile" button in Ed for Windows
- compile 4GL code from within Ed
- Ed shows compile warnings and errors in its Build results window.
You can also:
Launch Prolint from within ED for Windows to have it check the current sourcefile.
Prolint is a tool for automated source code review of Progress 4GL code. It reads one or more sourcefiles and examines it for bad programming practice
When you are interested Prolint, you are encouraged to subscribe to this group where you find the on-line tools to collaborate and discuss Prolint. There is a discussion forum, you can submit issues (for bugs and enhancement requests), you can modify the on-line documentation. So subscribe, and then don't forget to go to your subscription details to enable the e-mail notification!
Attached is the first version (written in OpenEdge 10.1a) of the Dataset.This program can show the contents of any dataset, including the records in the before table if present.
This project gathers various utilities related to parsing code. This includes tools for viewing or converting Proparse's syntax tree, utilities for find and report, utilities for search and replace, etc.
This program takes an XREF / STRING-XREF pair of files and translates them into a set of temp tables.
This is a code formatter program for alignment of a 4GL character base program.
This is an enhanced version of the Procedure Object Viewer made by Sebastien Lacroix at the Progress European Tech Support.
It has been optimized to handle ADM2/Dynamics Smart Objects or anything that involves super procedures. It includes a Code Viewer and a Smart Object Property Viewer, and has an optimized GUI (resizable, context saved...) Update on the 24-Sep-2004: -OE10 and 9.1D. Can generate override code or code to interact with an object when an entry has parameters -can copy into the clipboard: property name/value, object name, entry name -Custom filters on window title (such as container builder).
Integrated compilation of Web-Objects in the "Application Compiler". The application compiler is now able to compile *.html files. This file replaces the one that comes with the progress distribution.
Added by
Sascha Hoffmann
The Profiler Control tool can be used to perform profiler analysis of a Progress based application. The Profiler Control tool is designed to simplify the profiling and analysis of the performance data that the Progress run-time executable generates. This tool is a complete rewrite of the performance profiling tool that ships with some version of Progress. This tool includes a GUI for simplifying the launching and stopping of procedures. It has the ability to detect whether Progress Dynamics is running and allow the launching of dynamic containers as well as static smart objects and other procedures. It includes all of the same information, but removes much of the complexity of the previous tool by removing the requirement for a database and the timing consuming loading of profile data. In addition to previous execution statics, more information has been added. This tool also includes added functionality that gives the user the ability to perform side-by-side compares and exporting of data to external programs. Refer to the included Profiler_Readme.doc for a complete description.
The PUnit Unit Test Framework provides facilities to simplify writing test cases using Test Tools and organizing them into test suites hierarchy. The framework relieves users from messy error detection and reporting duties. The Test Runner procedure initializes the framework, sets up parameters based on command line arguments and/or environment variables, initializes the test suite and than runs the provided test suite. The framework keeps track of all passed/failed Test Tool assertions, provides an ability to check the testing progress based on the number of test cases run as part of the total number of test cases and generates the result report in several different formats. The Unit Test Framework is intended to be used both for simple testing needs and complex non trivial testing. It is not intended to be used in production code.