Re: please revive project 4GL++, using 4gl for Windows and New Era

I have customers that insist on using text screens via telnet, as well as GUI. The 4JS compiler provides us with this option. The before/after field validation stills works in GUI mode on the original unmodified code. New features are available for use in 4JS, as their should be in any future 4GL compiler. But a major project should not be required to modify your existing code base to be able to move to it. Rod Sheppard ----- Original Message ----- From: "Andy Lennard" <andy@kontron.demon.co.uk> To: <informix-list@iiug.org> Sent: Tuesday, May 20, 2003 8:29 PM Subject: Re: please revive project 4GL++, using 4gl for Windows and New Era > In message <bact7b$2fv$1@terabinaries.xmission.com>, Rodney Sheppard > <rod@transmit.com.au> writes > > > >I believe the most important thing for the future of > >4GL is that any compiler remain 100% backward compatible. > > > >If I have to go thru every line of code in every module looking for > >code that no-longer works, then the decision to move to another language > >is made for me. > > > > Please forgive me if my out-of-date knowledge of I-4GL is about to > show... > > We had (a very long time ago, I-4GL on DOS PCs) an application written > in I-4GL that attempted to do 'intelligent' screen navigation, for > example: > > Are the next 2 fields relevant? [] > Dependant field 1 [] > Dependant field 2 [] > Next question [] > > and used lots of 'AFTER FIELD' and 'NEXT FIELD' (iirc) to navigate > appropriately. > > When we tried to use 4GL-for-Windows, the users were able to point and > click into the dependant fields irrespective of the answer to the > preceding question. Had we moved at that time we would have had to re- > validate all our entry screens. I guess the same situation would exist > today. > > > -- > Andrew Lennard andy@kontron.demon.co.uk >