Re: [WDSCI-L] RDP: Are we our own worst enemy?

Scott,

I have user key actions set up to blockShiftLeft and blockShiftRight
(mapped to Alt-Shift- right or left arrow). Highlight a line or part of
the line then use the a-s-right and they move one to the right.

You can also change the default of the enter key action to split the line.

Window > Preferences> LPEX Editor> User Key Actions.

Jim


On Tue, Dec 18, 2012 at 9:09 AM, Scott Klement
<midrange-l@xxxxxxxxxxxxxxxx>wrote:

I agree with your suggestions, Dan. Though, I'd add one thing: The
only thing I use the line numbers for is RRT/LLT blocks to changing the
indenting level of code (shift the code to the right/left.) LPEX should
have another way of doing that. (Or, maybe it does, but is really hard
to find?)

I agree with pretty much everything you said here, though I do not use
the "wonderful Java editors" you reference.

Especially the enter key breaking the line -- this drives me up the
friggin' wall.


On 12/18/2012 9:29 AM, Dan Kimmel wrote:

The LPEX editors in RDP are fairly awful and need to be improved.
Those of us who work regularly in wonderful Java editors in the very
same RDP workspace are always aghast at just how clunky and awkward
LPEX is.

My suggestions:

Get rid of the line numbers on the left. I have a mouse; I don't need
CC,CC,A to copy a section of code. It's an SEU throwback that is in
the way of progress.

Put in a descent find/replace with regex support. Make it a popup
window instead of that silly box at the bottom. Don't reposition my
code/cursor when I hit ctrl-f.

Keep the outline up-to-date. I don't want to wait while an outline
generates.

The enter key should break the line at the position of the cursor. If
I want five blank lines, I'll hit the enter key five times.

Come up with some annotation comments and link them to the editor so
I can hover the mouse cursor over, say, a sub-procedure name and the
comments block (perhaps from some other source member) is diplayed in
a temporary text box. Use the javadoc methods, if necessary.

I can come up with more. I'll bet others have favorites, too.

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