|
Booth
"going to the web" doesn't necessarily mean rewrite everything with
JQuery.- there are products that can leverage existing skills with
screens and add things one could never do in 5250.
I don't want this to become a religious war on this stuff - just that
the phrase can mean different modalities. From a complete rewrite in
PHP to screen-scraping with customization options.
With a product to help, then concerns about GWT and XML and
touch-control and all become moot - any product worth its salt will
adjust to what is happening, methinks.
Cheers
Vern
On 9/21/2018 1:39 PM, Booth Martin wrote:
On its face this makes sense. On the other hand, "move to the web"
is not an easy choice for a large business operation because of the
relatively short life-span of the web's software. With a large
organization's 10 to 15 year development cycle, moving to the next
new best way every 3 or 4 years just not compute.
For instance... jQuery is in decline. GWT is gone. Liferay is gone.
xml is in the dumper. The mouse is being replaced with finger moves,
eye-control is on the horizon. This is all great stuff and is a
vibrant and exciting, but if you're a manager who wants to ship
product, bill product, meet payroll, and pay bills then providing
video games for the IT Department is way down your to-do list.
That's why I believe there is a strong need for us programmers to
figure out what we can do with 5250 to accommodate a new generation
of users who will never understand which is the F16 key. Yes; we
can offer check boxes, radio buttons, and dropdowns without being
disloyal to our heritage.
Wanting a reliable double-click is a reasonable expectation.
On 9/21/2018 8:34 AM, Raul Jager wrote:
I think it is better to move to web, rather than improve green screen.
No matter what you do, green screen will look old.
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.