The OpenEdge Hive

Version 1.7.2

• Added fix for conflict with other plugins that use Commons Logging.
• Added Groovy script engine and Groovy Console to the nav context devel utils menu.

Version 1.7.1

• First pass at a new Rename Files refactoring
• Some internal changes toward support on Tomcat

Version 1.6.1

• Proparse 3.1 with ABL 10.1B new syntax support.

Version 1.6.0

• Tree parser now gathers parameter information for calls and routines.

This report shows a snippet from each line of code where a database field is used. For example, a how-used report for sports2000.customer.custnum might show:

s2k\gui\bcust.w
define temp-table ...  like Customer.CustNum validate

s2k\gui\dcust.w
define temp-table ...  like Customer.CustNum validate

s2k\gui\dcust_cl.w
define temp-table ...  like Customer.CustNum validate

s2k\gui\orderreport.p
format ...  Customer.CustNum column-label "Cust-Num" format ">>>>9"
display ...  Customer.CustNum

s2k\gui\vcust.w
define temp-table ...  like Customer.CustNum validate

s2k\gui\vcust2.w
  

This is not the most efficient way to find where a database field is used, but it is a useful example of using ProRefactor.

See this WebSVN link for the full source.

It prompts for a fully qualified db.table.field name, checks that it exists in ProRefactor's configured schema, and splits it into two string variables: fieldName, and dbTableName.

It then finds all parse units in the directory of your choice, and loads or builds the PUB file for each of those, and then checks to see if your field is used in that compile unit. So, for each parse unit pu:

In prorefactor/projects/projectname/pubs in your working directory, ProRefactor writes out a parse unit binary (PUB) file for each compile unit in your application. These will be built as needed, when you do a parse or run a report.

These PUB files contain the full syntax tree and some additional information, so that your programs do not need to be re-parsed each time ProRefactor wants to get information about them. The *.pub files can be thought of a bit like your *.r files.

Here's the important bit: These files contain a fair amount of information, and will probably require more disc space than your .r files.

Using the standalone jar file, you can launch a command line console which contains one or two examples of how you can use the ProRefactor libraries. The console (org.prorefactor.Console) is the default class for the standalone jar file, so you can launch it simply with:

java -jar prorefactor.jar

Here's what its menu looks like as of Jan 2007:

h) How-used report
l) Load Settings for a project
p) Parse a directory
q) Quit
v) show proparse Version
w) Where used report

Enter selection:

Showing the Proparse version is useful for checking that the Proparse shared library can be found and loaded OK.

ProRefactor can be used as a standalone library, entirely independently of Eclipse.

This Java archive (jar) file contains ProRefactor, as well as the third party libraries it requires.

prorefactor.oehive.org/prorefactor.jar
Last updated: June 17, 2008. About a dozen MB.

Setting Up ProRefactor

1. See Project Config. Dump for a script which creates a prorefactor project settings directory.
2. 
   

This small package is for generating the configuration files needed by Proparse.

The zip file contains a directory named prorefactor. Extract it somewhere into your existing PROPATH.

Start your Progress development session, as usual. Your PROPATH, configuration settings, database connections, database aliases, etc., must all be fully set up as if you were going to compile the entire application. If you don't have these settings all correct so that you can compile your application, then Proparse won't be able to parse it either.

Then,

I've started work on a Prolint plug-in for Eclipse, but just written in Java, rather than ABL. Because it relies a lot on ProRefactor, I've just included my work so far in the ProRefactor SVN repository.

The Prolint/Eclipse page in the Prolint book is where you can find a bit more information and maybe a couple of pretty pictures. :)