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



John, you've got lots of good points, but I'd like to address a few of the
ones that I think are a bit misleading.

John King wrote on 20/06/2007 15:58:24:

The annoyances of the slowness of
refreshing RSE and retrieving source members,

I find that retrieving members is pretty darn fast most of the time. One
of my coworkers had major slowness retrieving source members. IBM support
determined that he had a "corrupted workspace". After creating a new
workspace, he can open source quite quickly. I do agree however that SEU
has the advantage in this race.


removing all those unwanted
"endif' statments whenever I edit some code

The automatic closure of block statements (for, if, select, etc.) can be
turned off in the preferences.


general mouse-clicky
style conflict with what I've grown accustomed to.

To each their own. I prefer vim to graphical editors for PC text files,
so I know where you're coming from. For me, there are enough advantages
to WDSC to overlook this - but then, I'm new to the System i world, so I
wasn't that quick with SEU to begin with.


For example, in SEU I
can call up a 2nd source member with shift-F3 faster than you can
even
think about grabbing your mouse, much less having to scroll through a
source list or setup some new filter pool.

That's what Ctrl+Shift+A is for. There are some WDSC operations that are
a giant pain in that they don't let you type library/source file/member,
but instead make you drill down through a list that take *forever* to
populate. For most of these, there are workarounds. As for filters and
filter pools - IMHO if you set up a filter just to access a source member
once or twice, you are using them incorrectly.


Certainly everyone should know WDSC and use it when appropriate, but
forcing its use for editing RPG and CL borders on micromanaging.

Despite "defending" WDSC, I agree with your statement, but would take out
the "for editing RPG and CL" part. Even for Java or HTML, sometimes
editing with a plain old text editor is the best solution.

Not trying to start a flame war,
Adam

Attention:

The information contained in this message and or attachments is
intended only for the person or entity to which it is addressed and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination or other use of, or taking of any action in reliance upon, this
information by persons or entities other than the intended recipient is
prohibited. If you received this message in error, please contact the sender
and
delete the material from any system and destroy any copies. Thank you for your
time and consideration.

Attention:

Le contenu de ce message et(ou) les fichiers ci-joints s?adressent
exclusivement à la personne ou -entité à laquelle ils sont destinés. Ils
peuvent
contenir de l?information confidentielle, protégée et(ou) classifiée. Il est
strictement interdit à toute personne ou entité autre que le(la) destinataire
prévu(e) de ce message d?examiner, de réviser, de retransmettre ou de diffuser
cette information, de prendre une quelconque action en fonction ou sur la base
de celle-ci, ou d?en faire tout autre usage. Si vous avez reçu ce message par
erreur, veuillez communiquer avec l?expéditeur(trice), supprimer ce message et
les fichiers ci-inclus de tout système, et en détruire toutes copies, qu?elles
soient électroniques ou imprimées. Nous vous remercions de votre entière
collaboration.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.