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

>>>"Hey, IBM, can you guys add the SEU prompting (IPC, etc.) to code/400? "
Will do. What other SEU functionality do you miss?

>>>"I sure wish they'd do something with the lame CLP prompting though!"
To be explicit, are you looking for GUI prompting? Is that it, or are there
other areas you would like to see improved, like formatting of the command
after prompting?

I also have seen a number of comments regarding the online help. We would
appreciate
details and suggestions in this area too. Timing is good right now to
influence the
product...

Phil Coulthard, iSeries AD,  IBM Canada Ltd
---------------------- Forwarded by Phil Coulthard/Toronto/IBM on
06/20/2001 01:31 PM ---------------------------

Chris Proctor <cproctor@gartsports.com>@midrange.com on 06/20/2001 12:50:04
PM

Please respond to CODE400-L@midrange.com

Sent by:  owner-code400-l@midrange.com


To:   "'CODE400-L@midrange.com'" <CODE400-L@midrange.com>
cc:
Subject:  RE: Inserting Specs of a different type after a given type.


Wow, Dwight! Don't sugar coat your words, come right out and let us know
how you feel! ha ha. I've been working S/38 and AS/400 since 1980 and I do
agree with you regarding the lack of prompting capabilities in the sequence
number.  I must admit, I was kinda' surprised to see that IBM didn't
include it. It is a pain to go thru the windows for prompting, but I just
end up typing the letter F,I,D,C,O, etc. in order to format the line
properly.  That is, unless it's one of the "special" formats, then I go
thru the windows.  Hey, IBM, can you guys add the SEU prompting (IPC, etc.)
to code/400?


However, Dwight, I still think that Code/400 is an improvement over SEU,
because of the validity checking as your coding and the instant help (when
needed). If you don't like it right now, don't use it.  I'm sure that as
time goes on IBM will get more and more functionality that will make our
jobs easier, then you can come back to it.


I sure wish they'd do something with the lame CLP prompting though! ha ha.
Did you hear that, IBM? ha ha.


Chris Proctor
Manager of Systems Intergration
Gart Sports
Denver


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





OK,


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.


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.


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

tool for new programmers, or people new to the computer, but we are people
who are in the business of producing code.


With SEU, we can type IPCX, IPC, IPO, IPI, etc. This technique is a bit
cryptic, but it is intuitive once you know how to program and it is quick
and efficient.


I know programmers who are playing with code to see how it works, but won't

commit to using it all the time because they can get to prompts faster
using
SEU and it is to time consuming and unproductive to fight yourself all the
time


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. Every time you make us
take
our hands off the keyboard to control the program I loose time. Finding a
little edit button, and point and click on undo can not be as fast as
reaching the top of the keyboard and pressing F5 to refresh the screen to
get rid of the last things I keyed since pressing enter. One keystroke with

my hands already in place.


I would like to see them add some of our basic functionality from SEU, back

into the program. Once it  is there and people feel confident when using
code it will gain wider acceptance.


I've heard a lot of noise about how good it is ever since it was announced
years ago and only recently had a chance to try it, and I have to admit it
in many ways has been a disappointment. I know part of my problem is the
new
way of doing things, but some things don't need to be done new ways.
Prompting the spec type is something every good editor has had since the
S/36 and S/38 because it is a good idea. Don't give up on 15 years or so of

a proven track record just for a novel point and click idea that is less
efficient.  You will have to take  SEU away before people will give it up
for code as it exists.


Dwight HoganCamp
Sturm Ruger Inc


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