RE: Re: Fullscreen application Specs

Hi all
 
HERE IS THE GOOD NEWS
There is no BAD NEWS.
 
The SAVE- FILE routines are now working - You can actually edit and then
save the file
Do the links and the proper access and you can edit and save anywhere
 
The B disk in the CMSUSER machine is proteced - I don't think you can get to
It because I crossed the passwords out in the copy of SIX pack DIrect that
you see - Pls let it reman R/O in any case as that where the programs you
are running sit.
Hopefully you cannot do the acces command on 191 (Mike Stramba) - which will
crash the system- same for 192 but don't try it on purpose.
 
On the A- disk you can destroy anything except  PROFILE EXEC
 
And you can link anywhere in the machine that you have access and do what
you like,
I copy the shadow files to the server from development machine so no problem
Be as adventurous as you like with the exceptions noted above and let me
know if you mange to kill the machine so I can put it back up
 
If you manage to kill it I have another test environment which I'd like to
recreate the issues in so be in touch..
 
Had a big problem with the copyfile command - seems to be doing something in
memory that I don't like and it kills the application.
The work around is this.
 
When you do a SAVE or a FILE
 
autosave old a is deleted
autosave temp  a is renamed to autosave old a
The file you are editing is saved as autosave temp a
If that failed any where you get a returncode
If not
then the real file wherever that may be is erased with FSERASE
 
A return code of 36 means that the disk is not accessed or is read only (but
have the autosave temp)
otherwise the old file is erased and the new file written again with the
proper name
Meanwhile no checking on EXIT or any of the important logic .  You say save
and it is saved.
 
 you can open as many sessions simultaneously as you want so use the editor
and the broswer
The machins is intentionally not too big - IhCW TO LOOK AT THE dumps
I LIMIT THE getvis area TO 6 MEG so too mamn large programs will kill the
storage 
Not sure how I recovover from that - Might need some work so stay away from
100000 line dumps
 
 If you get stuck with a file not accessed - your file is saved - Byou can
do the proper acces woth the CMS commands
or You can leave the application up with your changes and do the necessary
CMS coomands to acces the disk if you want
 
This is a multi user environment But during the development I sort of
skipped on the USER Signon
I don;t do anything with it -- so file names for all the temp stuff can get
overwrtten by other sessions.
Will fix that
 
I added three new commands
Yup you guessed it
 
FN
FT
FM
 
so you can open one file  ---> "test one a"  and they type 
FN KUKU
FT  PAUL
FM W
 
and when you do the save it will try to save it under the new name - You
should also see the new name displayed in the MAP.
Nice way to copy files
 
Anyway if no serious issues are forthcomng - This is the "ALPHA VERSION"
 
Anyone interested in Playing with it on your local Machine - can get the
installation on an AWS TAPE = TODAY
 
Since all the sources and listing are there also You can have it all It
emailable as a Zip File
 
If you are trying to understand it use the code and the llisting together -
Many macros that show up in listing wont mean anything in the code.
If you have a problem understandig something I'll be glad to help if I have
the time - Which I usually do
 
But I warn you  - at this stage I wont answer questions about changing  the
code.
Not until it is officially a BETA - Just too many changes right now
 
"C" programmers are welcome :-) suggest that they look at GCVC assemble for
a starter and GCIC.
 
I have finished stage 1 more or less on schedule. WHEW
Roc
 
Have FUN
 



  _____  

From: [email protected] [mailto:[email protected]] On Behalf Of
kerravon86
Sent: Thursday, August 05, 2010 10:48 
To: [email protected]
Subject: [H390-VM] Re: Fullscreen application Specs


  

--- In [email protected] <mailto:H390-VM%40yahoogroups.com> , "Rocky"
<rocsystems@...> wrote:
>
> Andy can make it part of the 6-pack if he wants 
> and I think that will
> improve the User experience for everyone.

Robert O'Hara releases that these days. You can't
ask for much more than a VM knight releasing it. :-)

> I will play around with the "C"

Cool.

> I am counting on you giving me advice and help 
> when I get to that stage.

Sure. Don't spend more than 10 minutes on anything
to do with setting up C. I will tell you what
button to press if you show me what you've got up
to in that 10 minutes.

And then we can head over to Beersheba to celebrate.
Water's on me.

BFN. Paul.

> From: [email protected] <mailto:H390-VM%40yahoogroups.com>
[mailto:[email protected] <mailto:H390-VM%40yahoogroups.com> ] On
Behalf Of
> kerravon86
> Sent: Thursday, August 05, 2010 09:50 
> To: [email protected] <mailto:H390-VM%40yahoogroups.com> 
> Subject: [H390-VM] Re: Fullscreen application Specs
> 
> 
> 
> 
> --- In [email protected] <mailto:H390-VM%40yahoogroups.com>
<mailto:H390-VM%40yahoogroups.com> , "Rocky"
> <rocsystems@> wrote:
> >
> > The way I wrote "C" it was almost assembler in any case.
> 
> As it will be on VM too.
> 
> > I'm pretty sure that most old timers work the same way -
> > If they don't have a tool box then they are not really pros.
> 
> I have a toolbox of utilities, but nothing that
> would really help with something like what you're
> doing.
> 
> Then again PDOS was a whole lot easier just having
> a C library to lean on.
> 
> > But "C" is fine - I never wrote it on the MF so 
> > I am a little apprehensive.
> > When I have a BUG in assembler I know its my BUG
> > A bug in "C" - I'm not sure.
> 
> I totally understand the apprehension - but please
> try generating a small C function:
> 
> int addnums(int a, int b)
> {
> return (a + b);
> }
> 
> and make sure you compile with optimization on
> (-Os) and I suspect that you'll be perfectly
> happy taking ownership of that generated code.
> 
> From then on everything's just a variation of
> the theme. :-)
> 
> Surely you can at least try it once, in 3 * 10-minute
> intervals? First 10 minutes is trying to find the
> compiler on your system and then reporting here
> what didn't work. Second 10 minutes is running it
> and asking here a question about R13. Third 10
> minutes is calling it from assembler and saying
> "Who would've believed it? It actually works!". :-)
> 
> BFN. Paul.
> 
> > From: [email protected] <mailto:H390-VM%40yahoogroups.com>
<mailto:H390-VM%40yahoogroups.com>
> [mailto:[email protected] <mailto:H390-VM%40yahoogroups.com>
<mailto:H390-VM%40yahoogroups.com> ] On
> Behalf Of
> > kerravon86
> > Sent: Wednesday, August 04, 2010 19:09 
> > To: [email protected] <mailto:H390-VM%40yahoogroups.com>
<mailto:H390-VM%40yahoogroups.com> 
> > Subject: [H390-VM] Re: Fullscreen application Specs
> > 
> > 
> > 
> > 
> > --- In [email protected] <mailto:H390-VM%40yahoogroups.com>
<mailto:H390-VM%40yahoogroups.com>
> <mailto:H390-VM%40yahoogroups.com> , "Rocky"
> > <rocsystems@> wrote:
> > >
> > > There is a lot of app logic involved here
> > 
> > And you're still not tempted to write any of
> > this in C?
> > 
> > While you personally are clearly very productive
> > in assembler, anyone else trying to debug a
> > problem or make minor improvements is going to
> > give up before they even start.
> > 
> > I see all assembler code on a dangerous road to
> > an orphanage. It's a dying art (a fact hidden
> > by the unusual nature of participants in these
> > Herc groups), while C programmers are 
> > permanently available at a dime a dozen.
> > 
> > BFN. Paul.
> >
>