RE: Re: GCIC Fullscreen Editor - Next steps

I see that quite a few have downloaded the package from my site. Some of you
also downloaded old documentation  about OS 2.10 and tied up my server.
 
Not too much feedback yet so I don't have any guidlines about what is
working and what is not.
 
1) I will make the fix for the Change/replace as dicussed as well as develop
a HEX routine,
   Both routines are complicated and will take some time.
 
2) I also want to do a small experiment with movng the application to a
higher position in memory.
   That will allow more functions to work from the CMS command - Not sure if
it will work and I will be testing that in the next couple of days.
 
3) The console will disconnect automatically when the application comes up (
that was the original design)
    I commented that out Because I was using the console for debuggng and
displaying memory during debugging - D PSW DUMP etc.)
    but that has caused confusion as some of you ignored the directions and
tried to use the console as some kind of input device while the
application was running. That does not work by design
 
4) If you reconnect to the machine the appliciation will automatically
finish.
 
5) with this scenario if you want to use it on your own machine instead of
as a server application it will disconnect and free up  your terminal for
editing - when you are finished just reconnect to your own machine - that is
not my ideal scenario but it is a alternative if you want it,
 
6) I have no plans to add any other functionality unless something very
basic is missing and makes the application unusable or seriously defective.
 
7) some one suggested a control function But currently the only control
command is EOJ and I will automate that.
 
8) if a Control functions is needed then it will be a full screen task and
not on the console
 
9) of course I will continue to support BUGS but not FEATURES at this time. 
 
We may revisit that in another couple of months to see if added
functionality is needed 
 
8) I am interested in using this platform/technology  for other applications
- any body have an ideas - Glad to partcipate   
 
9)  my next project will be a full screen debugger for this specific
technoloy - pretty diffuclt to Debug the muti taking environment with out
tools
 
10) we're missing help screens and I will be glad to support anybody that
wants to write them - Either indivual screens for the editor and the browser
and the FLIST - or a helpfile that can be browsed by hitting PF1  - think
about it and if any body has the energy I will help 
But I am not going to personally do it on my own just now - 
 
11) on another note I found a BUG in the sort routine  for the FLIST (on the
SERVER) - The date in the FLIST screen appears as DD/MM/YY so I will have to
change the logic a bit to shift the characters in the sort field. meanwhile
until the end of the month it is working.
 
If I am going to change/touch the fileds for sorting I think I will add some
Y2K logic to the sort algorythm  as well- 
If  YY >  50 then NI  YY,X'ef'
Just for the sorting not the displaying will get the proper order for the
old stuff - does that seem right?
 
 
Once I finish the Last two functions I will put together a Document in my
poor English of all the functions but if anybody wants to take over that
chore over I will appreciate it.
 
For those of you that have downloaded the ALPHA " Keep us informed of
progress on the testing"
I suggest that if it's usable and helpful that it be made part  of the
SIXPACK at somepoint in the future.
 
Roc
 
 



  _____  

From: [email protected] [mailto:[email protected]] On Behalf Of
paoloG
Sent: Monday, August 09, 2010 10:29 
To: [email protected]
Subject: [H390-VM] Re: GCIC Fullscreen applications Replace algorythm


  



--- In [email protected] <mailto:H390-VM%40yahoogroups.com> , "Rocky"
<rocsystems@...> wrote:
>
> Thanks Paolo
> 
> Thats good logic and I didn't think of using the LRECL as part of the
> algorythm
> Makes very good sense.
> 
> In the same vein perhaps we could use the FT as part of the logic as well.
> "C" "EXEC" "ASSEMBLE' "PLI" "COB"
> 
> Do you think I should try to identify if it is a program _ perhaps
> identifying - Assembler - C - PL1 
> that is probably doable very easily - and then I could tailor the logic a
> bit
> 
> And do you agree that shifting whole line is the right approach as opposed
> to shifting out multiple blanks
> 
> For instance:
> 
> ch /MVC/PACK/
> 
> MVC A,B original
> xxx1234xxx 
> PACK A,B eliinating mulltiple blanks 
> xxxx123xxx
> or
> PACK A,B Shifting Line
> xxxx1234xxxx
> 
> Would we want the A,B to line up or are we going to shift them.
> I think that TSO trys to eliminate blanks for certain scenarios
> and X-edit shifts the whole line
> 
> Roc
> 
> _____ 
> 

Rocky,
tailoring the logic on the FT would be nice; and eliminating extra blanks
would be a plus (an improvement over XEDIT).

Regards.

Paul