× 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.



Seriously. Just as amazed as I am when people tell me why they aren't using some form of client based development. I used to use SEU as most of us did, but now that I have gotten used to WDSC/RDi, it is like poking myself in the eye with a sharp stick trying to use SEU now. Yes, you can't always do things the same way you used to do them, but you arent stuck with doing things the same way you used to do them either. Too many advantages with RDi to stay stuck in SEU. The places I have been recently that weren't doing something with a dedicated dev environment like Synon 2E I have used WDSC/RDi. Two just bought the new RDi, one was looking for a new developer to hire on, and a key requirement for them was RDi. I know that some places are way behind the times, but what I have seen over the last two years or so is encouraging.

Mark Murphy
STAR BASE Consulting, Inc.
mmurphy@xxxxxxxxxxxxxxx


-----Dan <dan27649@xxxxxxxxx> wrote: -----
To: "RPG programming on the IBM i (AS/400 and iSeries)" <rpg400-l@xxxxxxxxxxxx>
From: Dan <dan27649@xxxxxxxxx>
Date: 04/01/2015 01:35PM
Subject: Re: Standard source file names?

Seriously? Client-based development for i (RDi, WDSC, etc.) is, in my
experience, by far the exception rather than the rule. Even in 2015. I
agree with your assessment that RDi negates the "ease of navigation"
argument, but this is a habit from my pre-RDi days. Otherwise, why bother
with all of the different source files if (most) everything is using the
source type to determine what to do with it? I still prefer the
"enforcement" of unique names that using one source file enables.

I've been gently warning folks here (a v7r1 shop) that I won't hesitate to
use new features that will trigger syntax errors in SEU. We currently have
5 RDi licenses, and I'm waiting for someone upstairs to sign the check for
an additional 5 so I can keep using my trial version after April 20th. We
have approx. 40 i devs here. A lot of old-timers supporting a legacy (i.e.
original on S/36) system.

- Dan

On Wed, Apr 1, 2015 at 12:51 PM, Mark Murphy/STAR BASE Consulting Inc. <
mmurphy@xxxxxxxxxxxxxxx> wrote:

It is amazing the number of "ease of navigation" arguments that are still
being used as RDi removes them by allowing you to open any source in any
source file with the same number of key strokes, or by grouping them
together in a common filter. I know a lot of folks are still on an old
release, but how many are using SEU with v7.1 or v7.2? There are a lot of
new features which are unavailable to you under SEU, at least if you want
SEU to provide even the minimal assistance it has in the past.

Mark Murphy


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.