Re: Future of 4/GL

Nils Myklebust wrote: > For programming database applications with character based user > interfaces there aren't many better tools arround. You just have to be > very aware of the fact that there is *no* migration route to GUI > programming. Not now, and not in the future. You have to rewrite your > whole application to go from 4GL to a true GUI solution. (Yes there > are stopgap solutions, but as 4GL programs aren't event driven there > is no way you can make them into true GUI programs without a rewrite.) > > Also be *very* carefull about claiming you will never need a GUI. You > may be proven very wrong. > Ahh, but I wasn't. There are a lot of applications where you won't need a GUI, and infact a GUI actually slows the process down. This occurs in order entry. Once a person becomes familiar with the interface and can type, they can really fly on standard character based apps. When they have to stop and point and click, then they have a problem. Also, cost is an issue. NCs are still 1K ($USD) while a dumb tty is $125 or so. In warehouse environments or manufacturing environments ttys get abused and have to be replaced. A hardened PC costs around 3K ($USD). So if you have a lot of data entry, then a 4GL app can offer a better cost effective solution. The point I was trying to make was that to start with a 4GL app has its advantages. First, if you are new to Informix and or Client/Server technologies, 4GL is a simple, COBOL like language which is easy to learn. This allows one to focus on the engine and database design. Once they have a base application, they can then port the app to a GUI if the app justifies it. (See above.) Also, using 4GL for the first app doesn't perclude you from switching to a different paradigm for the second or supporting apps. You can use GUI apps for data mining, or for analysis or for other forms of data entry or support. You can still re-use some of the first app if you write the business logic in C and use 4GL to C calls to access this. Also, you would want to re-write the app if you chose to port it to a GUI. The paradigm changes, as does the tools. But one of the advantages of having 4GL and *good* code, you can see the logic and work from an existing blueprint. 4GL is also great in writing reports. I could go on and on about 4GL but Kerry is already a strong voice on this issue ;-) The only thing missing is the Ronco Bass O Matic feature! I knew we should have pushed for it at the conference! ;-) [Its an American thang! ] -Just causing trouble, Mikey == #include <std_disclaimer.h> /* Mike Segel (MS385) */ #include <No_Spam.h> #ifdef OFFENDED_BY_CONTENT The author takes no responsibility for this post. Any resemblence to a coherent rational thought is purely coincidence. -The Management. #endif ***************************** Due to AGIS's Refusal to Act Responsibly We are blocking all of their domains at the packet level. This block will exist until AGIS modifies their policies to conform to existing RFCs and net community standards. We encourage all ISPs and domain holders to do the same. *****************************