message: 4
date: Fri, 12 Oct 2007 07:37:27 -0500
from: "Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>
subject: Re: [WDSCI-L] 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.
No not just when a file is changed but frequent enough to be annoying.
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?
Like locking up and dying is a good example. Like ignoring known bugs
that we were told were fixed in a future release.
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.
Part of the little things is the difference in indenting between the
conversion and when coding.
Select statements are done differently in coding than in converting. I
agree it is a small thing but you asked.
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.
The Snippets in WDSc don't work well by their own admission. If you
write a snippet for something that has to be fixed format with a
variable the spacing gets thrown off.
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
I never said I don't use it I just said that it does not completely
replace SEU. I didn't have to learn Java to write use SEU. I have a
problem with change just for the sake of change. Windows programs seem
to thrive on change just because they can. RSE is no exception. SEU
has made many changes over the years, but the basic functionality never
changed RSE can't say the same thing. I learned SEU in a few short
weeks enough to be productive and over the next few months learned other
aspects that made life easier. All without the aid of courses. RSE is
not that way. Just trying to figure out where to go to set things up
and then having them go away in an upgrade and not remembering where you
went in the first place. My job is not to learn Java, it is to produce
and maintain business programs that improve our bottom line.
I do enjoy our discussions though.
Bill
midrange.com
