Totally agree. In fact I used a web-based screen as the model for this
5250 program. The design goal is to consume .json with 5250 and to
present a more modern user experience.
My thinking is that 5250 shops with no intentions of going away from a
text-based system can, and probably should, consider efforts to move
past 1980's cram-the-screens-with-data and do-it-all-at-once workflow
models. Dropdown boxes, push buttons, scrollbars, and other
mouse-friendly features are no longer radical new cutting edge ideas.
A few days ago I asked if anyone is still writing 5250 programs and was
assured that yes, it's still happening in a big way. Therefore, it
appears to me that finding ways to bring 5250 into the 1990s, if not the
21st Century, is a reasonable goal.
Plus it keeps me out of the back alleys and beer halls. I had fun doing
this.
On 11/26/2019 10:17 AM, Raul Jager wrote:
It is a great job, only it looks kinda "old fashion"
Most of the same logic can be used to present an equivalent web screen.
This mailing list archive is Copyright 1997-2026 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.