jolly
VIP Member
Hi All,
This idea has been kicked around by myself and Alex Pastuhov before. jdeLogCentral is my latest effort at a toggle utility. It adds some (imho) very useful features: resides in/operates from the task tray, indicates logging state, waits for OneWorld when OW is not running and allows some editing of the jde.ini file.
Also, here is the first release of jdeLogViewer, the log view application. This thing displays a OneWorld client debug log in a tree form. This allows separation of threads into separate trees, and nested bsfn calls to be collapsed into outline showing the return value. It also allows on-the-fly execution of SQL select statements in the log (as long as you have an ODBC data source that contains the referenced tables). Naturally it has a bidirectional find as well.
Note that the viewer associates with the extension .owl. Therefore if you name your debug log to jdedebug.owl then accessing the View command from jdeLogCentral will invoke the viewer on the log file.
Note also: These applications require a registration code. The good news is that the registration dialog contains a link to a web page that instantly doles out an endless supply of 30 day registration codes.
All constructive comments welcomed!
Cheers,
JohnO
This idea has been kicked around by myself and Alex Pastuhov before. jdeLogCentral is my latest effort at a toggle utility. It adds some (imho) very useful features: resides in/operates from the task tray, indicates logging state, waits for OneWorld when OW is not running and allows some editing of the jde.ini file.
Also, here is the first release of jdeLogViewer, the log view application. This thing displays a OneWorld client debug log in a tree form. This allows separation of threads into separate trees, and nested bsfn calls to be collapsed into outline showing the return value. It also allows on-the-fly execution of SQL select statements in the log (as long as you have an ODBC data source that contains the referenced tables). Naturally it has a bidirectional find as well.
Note that the viewer associates with the extension .owl. Therefore if you name your debug log to jdedebug.owl then accessing the View command from jdeLogCentral will invoke the viewer on the log file.
Note also: These applications require a registration code. The good news is that the registration dialog contains a link to a web page that instantly doles out an endless supply of 30 day registration codes.
All constructive comments welcomed!
Cheers,
JohnO