|
-----Original Message----- Joe how do you handle the: We need both web & green screen interfaces cases with you methodology? ----- Revitalization was designed from the beginning to support the original green screen interface. After modification, the programs STILL RUN as green screen. They can even be maintained as green screen programs. The only thing you'll see in your main code is that display file I/O opcodes are replaced with calls to subroutines, like so: PSC dC** WRITELINCTL01 PSC aC EXSR PSCI01 That's it. If you don't actually have to change the screen I/O opcodes (and 95% of the time, you don't actually change the EXFMTs and WRITEs, you just change the indicators and the contents of the field), then you can maintain the program using SEU and it will work just fine. If, on the other hand, you do have to change how the screen I/O works, you simply run it through the converter again - the conversion takes just a few seconds. If you actually change the layout of the display file, obviously you may have some work to do on the UI end, although my goal for next month is to have at least a default user interface that can be used while you're tweaking the pretty version. My philosophy is that a company's largest asset is not only its legacy programs, but also its legacy programmers, and the idea is to be able to continue to test and maintain the original programs in their original green screen mode. If you use revitalization, the majority of your work can be done by traditional AS/400 programmers. No need to learn Java. If you want pretty HTML, you can even contract someone to do that work, and then plug it into the base stuff the tool generates. That's a little more involved, but the good news is you can do it at your leisure. The goal is for you to not have to learn any HTML to get the base panels working, and then spend time on "prettification" for only those screens that make sense from a business perspective. Joe +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.