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



Bryce,

I concur in your analysis but, in the name of fairness, you CAN scroll one
whole page in SEU (20 lines). Press F13 and in the first option select 'F'..

Again, I do prefer the use of WDSCi as a programmer's tool, even using the
SoftLanding RSE Extensions.

Regards,

Luis Rodriguez
IBM Certified Systems Expert — eServer i5 iSeries


On Mon, Mar 15, 2010 at 8:09 AM, Bryce Martin <BMartin@xxxxxxxxxxxx> wrote:

Yes it does produce the exact same object as. This is because it is just
remotely issuing a compile command on the IBM i. Plus, when I get any
errors or warnings with RPGLE source I can click a warning or error and go
directly to that spot in the code. No searching through source manuall
for *ERR or something like that.

The main advantage of RDi over PDM/SEU is in the time to analyze a program
and produce code. If you can see 86 lines of code (in my setup) at a time
in RDi(WDSC) versus only 19 in SEU then I don't know how you can ignore
the productivity gains that gives you. Add that to the outline view and
syntax highlighting. Even if the code wasn't colored and the outline view
didn't exist I would choose WDSC over SEU just for the increase in view.
Like I have said before, I wish I had a widescreen that rotated so I could
see even more lines of code. Everytime you have to page up or page down
you lose time. And SEU doesn't even page up or page down a whole screen.
Its like doing a half page up or a half page down (probably the most
annoying thing about PDM for me).

Its about programmer productivity and a programmer caring enough to
evaluate it from that stand point. It has nothing to do with the end
user, I have no idea where that came from.


Thanks
Bryce Martin
Programmer/Analyst I
570-546-4777



"Timothy Adair" <tadair@xxxxxxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
03/12/2010 05:04 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
midrange-l@xxxxxxxxxxxx
cc

Subject
Re: Change management systems






Thank you Scott!

Finally, someone cuts through all the opinions (on both sides) and gets to

the heart of the matter.

If programmer ABC writes the program in SEU/PDM and programmer XYZ writes
it
in WDSc/RDi, and the user sees and runs the exact same program, who cares
which programming environment it was written in? (Pardon the bad
grammar.)

Perhaps we need to remember that our primary purpose as developers is to
support the user. Period. Every user - from the data entry operator to
the
CEO.

Now that I'm done ranting, allow me to ask a question. Does compiling the

same source in PDM produce the exact same object as compiling it in
WDSc/RDi?





"Scott Klement" <midrange-l@xxxxxxxxxxxxxxxx> wrote in message
news:mailman.14503.1268429052.2580.midrange-l@xxxxxxxxxxxxxxx
Technically, PDM and SEU are not the same thing. But, PDM calls SEU
when
it needs to edit code.

They both come together as part of a package named ADTS. (Application
Development Tool Set) along with a few other things.

Personally, I think the advantages of WDSC/RDi/RDP over PDM/SEU are
being
constantly overstated in these forums. There are certainly some things
that RDi does better, like copy/paste, outline view, syntax
highlighting.

But these things aren't the ultra-awesome, revolutionary things that
folks
in these forums make them out to be. Yes, copy/paste is better in RDi,
but I could still do it in SEU, and I could do it pretty well. Yes,
outline view is useful, but searching out what I'm looking for also
works.
Yes, syntax highlighting/coloring can be nice, but I can read my code
okay
when it's all one color.

Personally, I think the user interface seen by the USER is far more
important than the interface seen by the DEVELOPER.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



--- This message (including any attachments) is intended only for the use
of the individual or entity to which it is addressed and may contain
information that is non-public, proprietary, privileged, confidential, and
exempt from disclosure under applicable law. If you are not the intended
recipient, you are hereby notified that any use, dissemination,
distribution, or copying of this communication is strictly prohibited. If
you have received this communication in error, please notify us and destroy
this message immediately. ---
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



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.