RE: Inserting Specs of a different type after a given type.

I've been using Code since it was only an OS/2 based system, so I guess I
have some experience with trying to find the fast path through coding.  I
use the ctrl/alt keys often, although I don't _hate_ the mouse at all, and I
basically can FLY through an edit session like there is no tomorrow.  If you
get to know them, they are fantastic, and WAY WAY faster than doing the SEU
shuffle.  Just takes a little getting used to.  I also completely agree with
the comment about giving up valuable real estate to sequence numbering and
dates.  It is fine to use them both for specific purposes, such as
diagnosing when lines of code were changed or inserted between various code
levels, but when outright editing I find them way to expensive to take up my
screen real estate... especially when doing Code Compare, where you have TWO
members up on the screen side by side and are at best seeing partial lines
anyway.

As for suggestions for improvement and CL prompting, please do away with the
need for a special connection (STRCODE) session just to enable CL prompting.
I seem unable to establish that anymore, and sometimes I DO want to prompt a
CL command.  Also, even when I AM able to get STRCODE going, it's not fun to
have to leave your editing session to go to another window to handle the
prompted CL.  It's great to NOT have to do that with RPG prompting, and CL
should work the same way.  All in all, though, my biggest complaint with
Code is that the history of problems and glitchy things (connectivity
issues, prompting issues, session freezups, memory leaks, etc...) makes it
difficult to convince NEW users to use it.  They find the old green screen a
more reliable and predictable interface, and thus would rather use that even
if Code provides for faster coding, giving the excuse that it can't be used
if it's down all the time.

Ric LuBell


-----Original Message-----
From: Dwight HoganCamp [mailto:Dhogancamp@Ruger.com]
Sent: Wednesday, June 20, 2001 3:02 PM
To: CODE400-L@midrange.com
Subject: Re: Inserting Specs of a different type after a given type.


OK

I'll print this information out and try it. I have seen a lot of those
ctrl/alt type keys used before, but everything in windows I have always used
was run by mouse, except the occasional program run from a command line or
DOS. I thought those options were for anyone who didn't have mouse
capability and have always just ignored them. Additionally, I haven't seen
any documentation of them from IBM. Not even in Violaine's book saying here
is a good way to run this.

They do have the ctrl/alt keys listed on the pull down menus, but that is
the only place I have seen it, unless there is something regarding the
tutorial on the web.

Thanks
Dwight  @ Ruger


----- Original Message -----
From: "Buck Calabro" <Buck.Calabro@commsoft.net>
To: <CODE400-L@midrange.com>
Sent: Wednesday, June 20, 2001 1:50 PM
Subject: RE: Inserting Specs of a different type after a given type.


> >Code is a wonderful tool that has a lot of really
> >neat search and find capabilities. These abilities
> >are useless if we can't do the basic functions
> >we know how to do in SEU.  Quickly and
> >efficiently modify source code.
>
> SEU is green screen, and suffers/enjoys green screen attributes.
> Code is PC based and suffers/enjoys programmable work station attributes.
> If you approach Code as an SEU substitute, you will never come to like it.
> Code is fundamentally different from SEU.  Whilst the functions
(cut/paste,
> insert/delete) are the same, the METHODS are, and should be different.
>
> >When adding a line of code, the program has gotten so smart you can't
tell
> >it what kind of line to prompt for when entering the prefix commands. You
> >have to enter IP, let it come up with a prompt based on the last line of
> >code entered. If it is right, you are ok. If not you have extra windows
to
> >display and select from to get your line added.
>
> Case in point.
> I didn't even think of using the SEU key template: I use LPEX.  I don't
want
> to see the sequence numbers - they take up valuable real estate.  Try LPEX
> with an open mind instead of SEU for a day or so. Alt+O, K, L, Enter (I
hate
> the mouse.) Turn off sequence numbers too - you'll start working in
smaller,
> more modular chunks!  Really!  Alt+V, N.
>
> >How many times does the spec type change in
> >a program? (F to IX to JX to C to CX to * to C
> >to CX, etc.) Every time it second guesses me
> >wrong, I have to waste time getting my code in
> >while I ask for the right prompt.
>
> Right!  That's why I never use it.  Actually, I very rarely prompt a line
of
> code.  The template at the top is plenty good enough.  If you Enter after
a
> line of text, you get a new line with the same spec type.  If it's wrong,
> you change the spec from (say) D to C, up/down with the cursor arrow and
the
> template reflects the C spec.
>
> >With SEU, we can type IPCX, IPC, IPO, IPI, etc.
>
> With Code, I type C, up/dn arrow.
>
> >All the attention to the mouse is a nice
> >add on, but you can not loose track
> >of the fact that we are still writing text code.
>
> I _hate_ the mouse.  I almost never use it.  There are keyboard commands
for
> just about everything.  Code is a Windows program which means it uses
> Windows standard keys:
> home - column 1
> end - end of line
> Ctrl+home - line 1, column 1
> Ctrl+end - last line, last column
> Shift+arrow - select text
> Shift+end - select to end of line
> Shift+Ctrl+end - select to end of file
> Ctrl+x - cut
> Ctrl+c - copy
> Ctrl+v - paste
> Ctrl+z - undo
> Ctrl+Shift+z - redo
>
> Buck Calabro
> +---
> | This is the CODE/400 Mailing List!
> | To submit a new message, send your mail to CODE400-L@midrange.com.
> | To subscribe to this list send email to CODE400-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
CODE400-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator: larry@paque.net
> +---

+---
| This is the CODE/400 Mailing List!
| To submit a new message, send your mail to CODE400-L@midrange.com.
| To subscribe to this list send email to CODE400-L-SUB@midrange.com.
| To unsubscribe from this list send email to CODE400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: larry@paque.net
+---
+---
| This is the CODE/400 Mailing List!
| To submit a new message, send your mail to CODE400-L@midrange.com.
| To subscribe to this list send email to CODE400-L-SUB@midrange.com.
| To unsubscribe from this list send email to CODE400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: larry@paque.net
+---