It's Time to Get out of the Stone Age
I use phpMyAdmin, and although I think the 5250 cursor sensitive function key interface is hard to beat to process business transactions, business software written with the complexity and style of phpMyAdmin would be potent, whether in PHP or RPGCGI or Java. I don't know much about RPGCGI (and even less about Joe's AJAX interface, for example), but if we can generate complex web pages that allow for multiple tangents of inquiry drill down within the screen via AJAX to support retrieving data or decision making for the transaction, and if we can support transferring the data from one focus area to another via a button click, it would be more productive than three or four 5250 sessions with limitation of cut and paste to transfer the data between screens, if not retyping as the norm. This is what I have been advocating for a number of years but felt the GUI must be OS based for intercommunication among the screens, desktop productivity apps, etc., which is what the customer wants and which web pages as islands insulated from the desktop do not provide for. However, AJAX does change the equation, and the intercommunication would be among the web page frames, giving even better productivity if the programming provides for the user changing the focus of inquiry frames as needed for ad hoc decision support during a transaction. It's true, Nathan, we don't have AJAX in 5250. Although now that I think about it it seems to me that a 5250 terminal emulator should be able to send on each keystroke or timeout, whichever came first, and the app provide an updated screen, subfile, etc., based on the keystroke and data to push ala AJAX. Keyboard centric is the key, though. rd
I use phpMyAdmin, and although I think the 5250 cursor sensitive function key interface is hard to beat to process business transactions, business software written with the complexity and style of phpMyAdmin would be potent, whether in PHP or RPGCGI or Java. I don't know much about RPGCGI (and even less about Joe's AJAX interface, for example), but if we can generate complex web pages that allow for multiple tangents of inquiry drill down within the screen via AJAX to support retrieving data or decision making for the transaction, and if we can support transferring the data from one focus area to another via a button click, it would be more productive than three or four 5250 sessions with limitation of cut and paste to transfer the data between screens, if not retyping as the norm. This is what I have been advocating for a number of years but felt the GUI must be OS based for intercommunication among the screens, desktop productivity apps, etc., which is what the customer wants and which web pages as islands insulated from the desktop do not provide for. However, AJAX does change the equation, and the intercommunication would be among the web page frames, giving even better productivity if the programming provides for the user changing the focus of inquiry frames as needed for ad hoc decision support during a transaction. It's true, Nathan, we don't have AJAX in 5250. Although now that I think about it it seems to me that a 5250 terminal emulator should be able to send on each keystroke or timeout, whichever came first, and the app provide an updated screen, subfile, etc., based on the keystroke and data to push ala AJAX. Keyboard centric is the key, though. rd
Comment