LOL Viking, but DO remember that Susan did call it terrible code.  Maybe you 
missed that part where she said it was bad, but made a good teaching example 
for the indent function and such.

Did I mention that it took less than 15 min for me to make ALL my views 
disappear Friday, as I jumped into WDSC with both feet? 

Yep!  I DO have talent ;)

Basticar, your performance with WDSC/RDi/RDp may not be great when connected 
to a remote System i.  However, when working remotely, the Projects 
functionality that Susan mentioned very briefly may be a good option for you.  
You work on it locally and then move it back up when you're back at work and 
connected.

By the way, I was very surprised that when presenting the features of a more 
modern development tool, Susan used an RPG source member that contained 
GOTO's, indicators for everything, and every other ancient technique that we 
now try to avoid!  But I guess that illustrates that even old programs can be 
maintained in RDi.

I just saw another presentation by Susan Gantner on RSE @ Ocean last week and 
I'm totally sold on it.  There are so many abilities it has compared to green 
screen; just wish I already knew it and didn't have to go through the painful 
learning process that any new and improved *anything* requires.

Right now I'm stuck trying to get my home PC (still on XPPro) to hook up with 
the iSeries at work.  I can already connect to my husband's at his office, so 
I know the RSE install on my PC is good.  I think the problem is that I need 
it to look for the secure host servers on the 9xxx ports instead of the regular
(default?) servers; but I can't figure out where I set that up > <

Service entry points are great.

Ringer.....

Do you think we should even mention "Debug" and how much better it is than with 
green screen?

The screen painter on RDI worries me the most, I still use CODE to generate
display and print layouts, the impression I've always had about RDI was that it
only allowed screen painting (I may be wrong in that, but IBM info indicates that)

I hate the amount of time it takes to install/Update WDSC is RDI even worse?

I like the editor on WDSC but it still seems easier to use plain old SEU sometimes.

I think the LPEX editor is awesome. But stay with SEU if:

> you like your code to display unicolored. 

> you like looking at less code in a smaller view.

> you are very careful and don't need an undo.

> you like manually matching IF/DOx/FOR/SELECT/MONITOR with the ENDxxx.

> you don't like bookmarks in the source code.

> you think FNDSTRPDM rocks.

> you don't want to edit the same source member in many views at one time.

Actually I love WDSc for what I "use" it for. I know it has it's quirks, but I 
definitely found I can get more done with having multiple members open 
(DDS/RPGLE) so I can bounce back forth to see Record formats, fields names, 
field definitions....
Cut/Paste

Still work the g-screens, but primarily i syat in WDSc

Ctrl-X/C/V work just fine in text mode. You have to use special key combinations
if you want to work with blocks of text.

I didn't like the looks of the DDS designer compared to CODE either. I've since
discovered that there's a DDS Design perspective, but haven't had a chance to
use it yet.

There are some annoying nuances, but I have no real problems with it - the 
benefits far outweigh those annoyances.  I love programming in it and feel 
claustrophobic programming in SEU now!

I'm still on WDSc (last version) Cut/Copy/Paste use standard windoze ctl+ 
keys.  Did they mess with that on RDP?

All good points, but the worst is the installation. It takes hours and hours to
download and then you have to run the installer multiple times to get different
pieces installed and then it doesn't install all that well. 

It also has java memory problems and workspace problems. 

The new DDS designer is truly awefull. The old CODE program was FAR superior.
Even SDA is easier to use.

i used to stand for integration, but now when you buy programmers tools, it is
piecemeal and needs to be put together like tinker toys. IBM must be reading
from Micronuts books as to how to screw up something. 

The ONLY good thing about having it is the outline view of the RPG program. 

No autocorrect

No intuitive way to do i-oriented anything (like add a library to the library list)

Times-out when you leave it idle for too long--forcing you to reboot or at best,
relaunch

The Manage Licenses "feature" (why doesn't it go away once I've activated?)

Font management/adjustment (where's the "apply to all" button?)

Cut/Paste/Copy controls don't use standardized Windows Ctrl+X/V/C

Takes too long to make quick changes

Finding the install image, downloading it, and activating it is too complex

Each new release makes it faster but less reliable than the previous, but data
(i.e., source code) is almost never lost.

more to come...