RE: Re: Full screen application Specs

 


  _____  

From: [email protected] [mailto:[email protected]] On Behalf Of
Mike Stramba
Sent: Monday, July 26, 2010 19:07 
To: [email protected]
Subject: Re: [H390-VM] Re: Full screen application Specs


  

Hi Roc,

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

Yup But I an't get a job because I am too OLD - Ten of the youger generation
would work a year to get to the same result as we have here 
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
  Probably doable but I am not sure I want to spend time on tht kind of fine
tuning right now - Lets put ii in to do list

Now I want ot concentrate on gettin a working framework - Goal was one month
- Don;t know if I can make that but don;t want to miss by too much- Wife
wants me back 
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)
 thats a big issue - it would mean a lot less data on the screen - I guess I
could add the two positions to the three I have in the action field now -
something like x-edit but that becomes confusing for commands. Again - that
is not trivial and I shoud probably do it now but it is a lot of work that I
want to avoid right now --- Solets put that in the TODO list also - when we
get working I promise to come back to that.   

 
3) Caps .. has to be an option ! :) Even the lowly CMS editor has that !
 AGREE --- I;ll do that next week or later this week 
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)
 Forget about option menues ---- Whneit becomes a commercial ting I will
oputin options now lets get it working - 
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
 MOST editors work the way I describe - The copy would be automatic and then
I would erase the file on the 'A" disk but if it failed you done want to
lose your editing.

 
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 ;)
 OK - then I will process the action lines and ignore the command line if
the option lines have data 
Mike