Re: Re: Full screen application Specs

Hi Roc,

You are one seriously efficient "coding machine" ;) ...  guess 40
years of practice will do that

1) After an "i"(nsert) line(s), the cursor should go to the editing
area of the first line inserted, (it's going back to the command area)
now

2) Are you planning on adding line numbers?
 (internal to the editor .. not saved with the file ... and    some
kind of "goto" line number command (I like the mneouminc "g"
personally (but an optoin menu to define preffered short cut keys
would be nice too)

3) Caps .. has to be an option !  :)  Even the lowly CMS editor has that !

4) > what is the logic for SAVE - PF3 automatic save or save only on
SAVE or FILE

I'd like to see that in an option menu (or if an editor.cfg file of some sort)

5) > I don't think I should do a save directly but rather  a save on the A DISK
> under a different name and then a copy

Again, make "backup files" an option.  less cluttered disk vs "live on
the edge / user takes responsibility for enough disk space etc"


> Is a good rule of thumb to process the action lines on theleft side first
> and then process the command.
>
> for instance  - that would work find for DD DD OR CC CC
> Or should I ignore the command line when their are action fileds - that
> makes the logic a lot easier
> just process the action lines

The only example I can think of where both action lines / command line
are both enabled /usefule, is if a "dd" is entered on first line, then
it's possible (in ISPF anyway), to search for a string / goto a line
number to then add the matching "dd".   More a luxury than  a
neccesiity ;)

Mike