× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Completely agree with Jon Paris on this one.

I’m used to PDM. No joke.
Also I’m used to the dumb terminal keyboard mapping from old days. Again no joke.
So I always map my keyboard to that of the dumb terminal keyboards. Lol. No kidding

Am I fast? Yes
Do I write modern RPG ILE and C programs? Yes.
Does the editor light up bright green. Yes.
(Though I can turn it off but it helps keep me awake).

But who cares I’m very fast and very efficient.

Having said that I do use VS for other languages such as C# and goLang.

And must say RDI is a great editor as well.

Jay

On Nov 3, 2021, at 1:51 PM, Brad Stone <bvstone@xxxxxxxxx> wrote:

I just made the switch from ILEditor to VSC. The one thing I wish it had
was when adding source PFs to your list, you could just say

LIB/Q*

And it would load them all. Instead it seems you have to do each source PF
at a time.

Of course, I imagine my next step would be moving to the IFS for source
instead of source PFs. :) But honestly I don't see much of an advantage
to that. And I haven't tested if wildcards work there either.

One other thing that gets annoying is after a compile where the errors and
warnings are listed those lines all get squiggly lines (like ones for
typos) on them.. combine that with all of the nesting lines for loops,
if/select/etc... and it gets messy pretty quick.

Finally, I haven't figured out a way to open the same source member twice..
as someone said they did. It would be cool to have one open in case you
fat finger a copy/paste/etc to see what it was before.

On Wed, Nov 3, 2021 at 10:41 AM Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>
wrote:

Jon,

I think you just hit on the one reason I might add it to the toolbag, quick
edits on primarily CL code, of which I do quite a bit. RDi, unless it's
already open and connected to that system, is usually more work than just
using SEU to make the change and compile/test.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On Wed, Nov 3, 2021 at 10:17 AM Jon Paris <jon.paris@xxxxxxxxxxxxxx>
wrote:

It is very much a case of what you are used to I think.

I have been using RDi and other Eclipse based tools for many years. I
find VS Code completely non-intuitive (as indeed I do most MS products to
be honest).

The biggest advantage that I find with VS Code with the IBM i extensions
is speed - I now use it in all cases where I might otherwise have been
tempted to use PDM/SEU rather than power up RDi.

But for any serious development I still go back to RDi because I can't
live without Outline view. The other big advantage to RDi is that I can
drill down through trees or use filters and that can fill the screen if
needed. The VS Code model is far more restrictive and doesn't give me
those
same options. It is a great tool and I unhesitatingly recommend it for
shops where RDi's price is a barrier but I don't see myself giving up RDi
for a year or three yet.


Jon Paris

On Nov 3, 2021, at 10:09 AM, Maria Lucia Stoppa <mlstoppa@xxxxxxxxx>
wrote:

Hi Jim,

I agree with Tim.
Given that I already use VSC for web languages and I usually have an
open
5250 session, I found it much easier to use just one editor for all the
languages, instead of switching among many.



Il giorno lun 1 nov 2021 alle ore 20:09 Tim Fathers <tim@xxxxxxxxxxxxx

ha
scritto:

In my case I find VS Code a far superior editor to anything Eclipse
based,
especially RDi, and I use it for every other language I develop in.
Unfortunately, the IBM i extension for VS doesn't work properly for
me, it
stopped reporting compilation errors for some reason and I haven't had
time
to work out why yet.

Tim.


________________________________
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> on behalf of Jim
Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>
Sent: 01 November 2021 17:54
To: RPG programming on the IBM i (AS/400 and iSeries) <
rpg400-l@xxxxxxxxxxxxxxxxxx>
Subject: Visual Studio vs. RDi.

OK, aside from the cost of RDi (not really that high when you consider
support, etc.) why would I use Visual Studio over RDi? I think VS is
fine,
no argument with it. Same with ILEditor. If you have a license for
RDi,
what's the rationale for using something else?

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects
--


--

Maria Lucia Stoppa
mlstoppa@xxxxxxxxx
--


--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.