Buck,

Yes, by "replace" I mean a strategy of modernization involving replacement by deprecation. We deprecate 5250 green screen development. It's no longer preferred for new development. The preferred UI is now web or mobile (or both). Over time, the percentage of 5250 green screens in production decreases, and the percentage of web\mobile UIs in production increases. So the 5250 green screens are gradually replaced over time.

We have no plans on re-writing existing 5250 green screens. We would consider it if there was an ROI or a compelling business case. But that would be the rare exception rather than the norm.

We will also continue to develop a small number of 5250 green screens when users need to do rapid, heads-down data entry. 5250 green screens are actually good at that.

Thanks,
Kelly


-----Original Message-----
From: WEB400 [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Buck Calabro
Sent: Tuesday, May 26, 2015 10:29 AM
To: web400@xxxxxxxxxxxx
Subject: Re: [WEB400] Single Page Applications

On 5/23/2015 10:42 AM, Kelly Cookson wrote:

I just don't see a reason to avoid SPAs for replacing 5250 green screens when so many website are successfully using SPAs in the wild. Many people feel the experience when using an SPA is faster and more fluid than the experience when using traditional web applications. The users get a more desktop-application-like experience. A faster, more fluid, more desktop-application-like experience seems like something one might want when replacing 5250 green screens.

In my past lives, 'replacing 5250 green screens' has been a code word for 'screen scraper'. Which isn't evil in and of itself, but the practical results of a traditional block-mode application [1] with a web UI has been horrible to these eyes.

So I hope that here, in this discussion, 'replacing 5250 green screens'
really means' write a whole new application from scratch.

[1] A typical 5250 block-mode application, Order Entry:
Screen 1: Enter customer number, verify customer name/address. F key to search for customer based on name/ telephone number.
Screen 2: Display customer name/address, enter ship to information. F key to recall previous ship to information/same as sold to.
Screen 3: Display sold to/ship to, enter product information.
Screen 3 repeats until a function key is pressed to 'finalise' the order Screen 4: display totals, taxes, estimated ship date.

I might be able to make wonderful CSS and AJAX and convert this to an SPA which calls the appropriate Cobol program under the covers, but this behaviour is not remotely similar to what one experiences with say, Amazon.

--
--buck

--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing list To post a message email: WEB400@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/web400.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.