Re: Resistance to using RDi

I can be slow to embrace new stuff. I still know where my OS/2 disks are.

I use RDi regularly and love it, even though I probably use/understand less than half the features. For instance, the debugger still throws me for a loop.

Having said that, I am trying to remember the features that made me stay with RDi, and the features that I would miss if required to use SEU/PDM.

-One is that I can work offline.
-Another is that I can group a project all together.
-Also I can work on the same program in two different areas at the same time.
-Having a search/replace feature that is versatile, fast, and clear is a real bonus.
-Expand/collapse lists so that in one left hand pane I have clickable access to, probably, 500 source members over several machines. All searchable with a few clicks.
-The editor itself is leagues ahead of PDM.
-The error list from compiles is a real winner for me. Click an error to take yo to the place of the error, fix it, have the error checked off.
-Verify-as-you-go editing points out a lot of my typos.
-The really big deal, for me at least, is Ctrl-z.

I believe that focusing on those few items will convince most programmers to give RDi a shot.

date: Wed, 17 Feb 2016 18:57:09 -0500
from: Buck Calabro <kc2hiz@xxxxxxxxx>
subject: Re: [WDSCI-L] Resistance to using RDi

...My notion of success is that they become almost immediately

enamoured of RDi and constantly walk past my desk to shower me with
adulation for finally bringing them to the promised land.
...
--
--buck