Re: 5250 to Web Interface / Application Modernization -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

On Mon, Apr 8, 2019 at 3:46 PM Jon Paris <jon.paris@xxxxxxxxxxxxxx> wrote:

An OA solution is not limited to the 5250 paradigm and so does not really
belong in the same category as screen scrapers. Not to say it isn't used as
a sophisticated version of those but it is by no means limited to that
design scenario.

I feel that the workstation record-write, record-read paradigm is not
fitting for web interfaces. Yes, it appeals to legacy application
developers. Yes, you can force-fit it via OA. But you give up the ability
to respond to any type of event that may occur at any time within web
browsers. That's a constraint that I wouldn't be willing to accept.

I'm tempted to delineate Web UI designs that don't fit the workstation
record-write, record-read design pattern. But it seems that the point
should be intuitive, and sufficient.

Screen-scraper proponents argued for years that their interfaces weren't
constrained by the 5250 paradigm, saying that the screens could be
extended. But people ran into constraints, nevertheless.

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.