Also, there are also many ways to customize WDSC to be able to use tools you are used to.
Check out
http://wiki.midrange.com/index.php/RSE for creating user actions in WDSC.
Maybe you can use RPGTOOLBOX commands as user actions.
Also the compile commands are customizable. WDSC, when a source member is open, (menu compile, work with compile commands).
I just started with snippets in the last few weeks and they work well for me.
I just copied some from my Snips source file that has been building up for years.
hth,
Dave B
"Dave Shaw" <daveshaw@xxxxxxxxxxxxx> 10/12/07 9:29 AM >>>
Bill,
I can't speak to RPGTOOLBOX - it's outside my experience. I've changed jobs
enough over the last 10 years that I haven't been able to become hooked on
such things. It would be nice if WDSCi made it easier to share user
actions, snippets, templates, and so forth, and I hope the developers have
taken note of that, but I don't consider it a drop-dead issue. Maybe I'm
just self centered. ;)
As for your compile problems, I've had a few, too, but they've all been my
own fault. Library lists that I thought matched but didn't, compile
parameters that I thought I had set the same but hadn't, etc. You have to
look at the error and determine the cause to fix it. It most likely isn't
WDSCi itself, since I don't see a lot of those kinds of complaints that
can't be solved.
Of course, I'm coming at this from a very different direction than you are.
I haven't used SEU in more than a dozen years except in emergencies. I
started using flex/EDIT (the original DOS version) in '93, switched to the
Windows version when it came out, switched to CODE/400 when I changed jobs
in '99, and only just switched to WDSCi when I got a new laptop last winter.
SEU is NEVER faster for me than WDSCi, for the simple reason that my fingers
have forgotten it. I don't even like browsing in it. When you start
hitting Ctrl-Home automatically to go to the top of your source and curse
the crosshair for going on or off, and have to think for a minute to
remember that you need F10, T, enter, you'll know what I mean.
As for those complaining that absolutely everything can't be done from
within WDSCi yet, I agree with whoever said that Alt-Tab to the green screen
doesn't take that much time, and I still prefer it to the Arcad emulator,
which is still a bit buggy and doesn't do some of the basic things that I'm
used to having in Client Access. To those complaining, I would suggest that
you tell the developers how you want it to work and why that would be
better, rather than just ranting that it doesn't do it. Just a suggestion.
I better get off the soapbox.
Dave Shaw
Mohawk Industries
----- Original Message -----
From: "Bill Barnes" <bbarnes@xxxxxxxxxxxxx>
To: <wdsci-l@xxxxxxxxxxxx>
Sent: Friday, October 12, 2007 7:51 AM
Subject: [WDSCI-L] Green Screen Plodders.
message: 1
date: Thu, 11 Oct 2007 12:08:24 -0500
from: "Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>
subject: Re: [WDSCI-L] Fed up with green screen plodders
From: DennisRootes@xxxxxxxxxxx
I personally don't see WDSc/Rational replacing the green screen until
it
fully supports interactivity. The way it's done now bites. I do most
of
my coding in Rational, but compiling and other interactive stuff on
the
green screen. But that's just my opinion. =)
What are you looking for, Dennis? An emulator view in WDSC?
Compiling and so on can be done via WDSC, but I agree that testing green
screen requires an emulator. But do you want an embedded emulator just
for
running the program? Why is that any better than using iSeries Access?
Joe
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. WDSc still has problems, albeit
small ones, but they are annoying. The RPG Converter is not near as
robust as RPGTOOLBOX from Linoma. 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.
Bill
midrange.com
