Re: Green Screen Plodders.

From: Bill Barnes

I have had problems compiling with WDSc and have gone to the Green
Screen to compile and had the program compile successfully. Library
lists were identical on both sides.

Since when? The only time I run into that issue is when I make changes on
the host (such as adding new fields to a file) and don't refresh my cache.

WDSc still has problems, albeit small ones, but they are annoying.

Such as? I mean, other than where it doesn't match up to Linoma's tool,
where is it lacking?

The RPG Converter is not near as robust as RPGTOOLBOX from Linoma.

I agree on this one. There is a need to explain to people how to prepare
their programs for conversion to /free.

Snippets in WDSc are not as friendly
as RPGTOOLBOX and can't be easily shared. I will start out a new
program on the Green Screen because I can use a snippet I wrote to
create a shell program with all the standard names and structures this
shop uses. In WDSc the shell produced needed a lot of tweaking manually
before it was useable and was more trouble than it was worth. If Linoma
ever makes a plug in for WDSc for their RPGTOOLBOX package it would
certainly help.

This is not standard SEU functionality, Bill. If you wanted, you could
write your own plug-in to WDSC to do this sort of thing, and Buck has been
telling us about a macro scripter that can be installed. The fact that WDSC
doesn't do what RPGTOOLBOX does is not a knock on WDSC, it's just your
preference for a third-party tool--one that doesn't support WDSC.

I don't mean to argue, Bill. Are the issues above a legitimate reason to
not use WDSC? Maybe they are for you. But then again, maybe if you
invested some time in learning the scripting tool or even learning Java, you
could extend WDSC yourself exactly to your liking and be even more
productive than with the Linoma tool.

It's just a thought.

Joe