Description

Some Progress Editor extensions, to add convenience and robustness to the developer.
Supported by all versions \ OS \ Terminal environments.
Open Source.
Author: Yuval Papish
Homepage: http://www.yuvcom.com/ProgressEditorExtensions

In the AppBuilder there is a propath compiler – of sorts. It is more like a collection of paths and it is up to the programmer to sort it all out. Once you move onto another project – that's right, you loose all those configurations should you need to come back.

This is something distinctly missing from the web based programming tools too. There doesn't seem to be a tool that will walk up and down the propath looking for HTML to convert and .p/.w's to compile. I have encountered applications with so many files in them, the File Tools in

Converts progress app builder aliases to open edge architect macros.

My window with the codejock components is ready for beta testing. I now needed to make an installer for the runtime version of the components. Some weeks ago I came across NSIS (Nullsoft Scriptable Install System).

In less than an hour I was able to create an installer with it.
I've attached a simple nsis source. It expects the runtime version of the components, found in cab files in %Program Files%\Codejock Software\ActiveX\Xtreme SuitePro ActiveX v11.1.0\bin\Redist, to be extracted to a subdirectory Components.

This program reads log files for logentrytype dynobjects and produces an output of those log file entries where objects were created, but not deleted.

Reads output from a LOG-MANAGER:LOG-ENTRY-TYPE = "4GLTRACE:4" and reports the line number, date, time, statement elapsed time, total elapsed time, nesting level, action, action adjective, and remaining data in a columnar format

I am working on a manual of code standards for my division, and would appreciate input about this. I've incorporated (or adapted) many of the entries from the prolint lists of bugs, style improvement, performance enhancements, etc. Of course this will be a combination of helpful advice, common sense, ways to make the code more readable and re-usable, and ways to prevent problems down the line.

I will appreciate any suggestions or ideas that are sent in.

ProUnit is a framework to create automated unit tests for Progress 4GL platform. It's based on other XUnit frameworks, like JUnit, NUnit and others.

The Widget Walker (also known as Widget Viewer and AttriVitoque) is a tool developed by Vito Imburgia at EMEA ETSC.

It helps a developer to preview what they can implement in 4GL (walking from one widget to another, changing an attribute, applying a method or an event) It's really effective when it is set in the proTools.

Listing of Articles and presentations written/presetned by me