Re: Skeleton records and auto indent missing in JLPEX? -- WDSCI-L




There are macros available for CODE (not LPEX) that can help with copying
lines, modifying blocks of data, enhancing CODE tools and others you can
write yourself in ReXX.  These are completely free and available at
http://faq.midrange.com under Programming > CODE/400 > CODE/400 ReXX
Macros.  Some of my most used macros are the ones so you don't have to
press Alt+L if copying 1 line and the RPG Smart Enter temporary toggle.
Check out the RPG Smart Enter in CODE under Options > Lanuage Editing >
Smart Enter > Enable Smart Enter.  I use this option for RPG almost all the
time.  After writing the Smart Enter toggle, I added this as a request to
the IBM FRED (Frequent Request Database)
http://www7b.software.ibm.com/wsdd/ on June 23.  This had another vote but
I haven't heard any IBM response.  Someone suggested adding it to the FRED.
Is someone from IBM reviewing the FRED?  I even have a macro to create a
subroutine (like the create procedure).  Another macro can change
modifiction dates and modification marks in blocks sort of like in SEU but
with more options.  I admit this modifiction block macro I wrote has bugs,
but it can save you time since there is nothing else available.  Some
macros were started by some programmers and finished by others.
Supposedly, you can write macros for LPEX in Java but I don't know anyone
who has and I don't have the time to learn and convert these macros.
In years of SEU use, I have found that CODE does basically everything SEU
does and better.  So, I think CODE is SEU on steroids but LPEX might be
like a junior CODE for now.  For the IS (Insert Skeleton), I would probably
use Ctrl+C then Ctrl+V but I could see where you would want a block over
and over.  You could create a macro containing whatever lines you want and
then assign it a function key.  Add it in a menu and you could select the
skeleton you want.  With some of these macros, we can fix and enhance some
of those functions IBM fumbled or didn't think about continuing.  If there
is some language editing function you want that CODE doesn't have,
sometimes you can write your own macro.  IMHO, I don't think IBM will spend
any time enhancing CODE as I think they are pushing LPEX.  Could IBM look
through some of these macros, enhance or fix them, and integrate them?  I
think most of the programming work is done, it just takes IBM to look over
them, endorse them, and inegrate them.  I hate to work against IBM since
they write functions so well, but if they stop enhancements or even refuse,
we need to work around them.  It appears they are aggressively fixing
functions though.

Thanks,
Craig Strong

** Vern wrote:
<snip>
So these are things that USED to be there and are no more. <small rant>
Please don't call WDSC "SEU on steroids" when these simple things, IMO, are
missing. </small rant> Please continue the good work you are doing, to find
out what is really in SEU that helps folks like me.
<end snip>