<snip>
FWIW we're building new applications using the same HTML, CSS, and
JavaScript constructs that we were using 10 years ago. I don't see that
changing in the foreseeable future. We've deployed over a thousand
interactive applications and reports this way. </snip>
Nathan, while we have dipped our toe in the water as to speak with a web
portal providing basic portal like functions (account balance, reprint
statements, update contact details ... etcetera) using php we are now
starting a bigger project using the 80/20 rule. 20% of the programs (menu
options) are used 80% of the time so by providing those first with a GUI
via the browser is our plan.
The number of users is never going to be large (per system) and our
vertical market is never going to large - very niche solution.
I would be interested in any suggestions or recommendations that you may
think would help us in putting a good foundation in place.
Thanks
Don Brown
From: "Nathan Andelin" <nandelin@xxxxxxxxx>
To: "Web Enabling the IBM i (AS/400 and iSeries)"
<web400@xxxxxxxxxxxx>
Date: 01/03/2018 04:14 AM
Subject: Re: [WEB400] Express, React, Node.JS
Sent by: "WEB400" <web400-bounces@xxxxxxxxxxxx>
On Tue, Feb 27, 2018 at 3:13 PM, Booth Martin <booth@xxxxxxxxxxxx> wrote:
A decent GUI makes sense but I must admit to the constant starting over
as
getting pretty old.
FWIW we're building new applications using the same HTML, CSS, and
JavaScript constructs that we were using 10 years ago. I don't see that
changing in the foreseeable future. We've deployed over a thousand
interactive applications and reports this way.
There is of course a lot of churn in the UI front. But one doesn't have to
get caught up in it. Good design is resistant to obsolescence.
midrange.com
