From talking to the sales & service agents at ${COMPANY} after prototyping some 'New Generation' systems we determined that Web-based UIs had two advantages:
1. Multi-column layout with independent updates. Useful for presenting prompts and help information beside the main transaction window.
2. AJAX-style dynamic updates on data-selection.
Other than that there were few advantages to Web UI. In fact we had to spend some time developing Javascript functionality such as tab-order and F-key capture that are elementary, 'free' features with green-screen and which greatly improve transaction speed.
Any 5250 terminal emulator from the 1990s onwards offered copy-and-paste and multi-session capabilities so a Web UI didn't offer advantage there.
On what TUI systems is a multi-column layout not possible? On what TUI systems are dynamic updates not possible? In my experience, teletype or ssh is much better in this regard, as the systems use socket connections which support push, which allows updates to propogate faster and more efficiently than using http (I know, http2 improves this system, as well as websockets, but those are recent arivals and only serve to play catch-up).
Comments
From talking to the sales & service agents at ${COMPANY} after prototyping some 'New Generation' systems we determined that Web-based UIs had two advantages:
1. Multi-column layout with independent updates. Useful for presenting prompts and help information beside the main transaction window.
2. AJAX-style dynamic updates on data-selection.
Other than that there were few advantages to Web UI. In fact we had to spend some time developing Javascript functionality such as tab-order and F-key capture that are elementary, 'free' features with green-screen and which greatly improve transaction speed.
Any 5250 terminal emulator from the 1990s onwards offered copy-and-paste and multi-session capabilities so a Web UI didn't offer advantage there.
On what TUI systems is a multi-column layout not possible? On what TUI systems are dynamic updates not possible? In my experience, teletype or ssh is much better in this regard, as the systems use socket connections which support push, which allows updates to propogate faster and more efficiently than using http (I know, http2 improves this system, as well as websockets, but those are recent arivals and only serve to play catch-up).