Re: GUI vs Green Screen was open source IBM i. was Re: From RGP to ¿Java ?

Nathan,

We've done browser-based data entry applications with good
performance. The main issue is key mappings. We found we had to pick
one browser in order to deal with F keys. Actually, we probably could
have abstracted F key handling a bit better and made it cross-browser,
but our client had standardized on IE anyway.

Mike E.

On Tuesday, May 12, 2009, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

From: Kurt Anderson
I'm pretty proud to say that at my previous job, our team
developed a GUI order processing system that the users loved.

What did you use for the GUI?  Visual Basic?  Java (Swing or AWT)?  Screen Scraper?  HTML?

I promote browser technology for applications, but must admit that I've never created a browser-based GUI that offered the same level of keyboard support that's available in green-screen applications.

The most resistence I've seen to GUI was with screen-scraper products.  My daughter has a part-time job at a bank, and was given the option of using a green-screen interface or a (JWalk or NewLook) GUI interface.  She chose green-screen for performance reasons, and made the decision without any input from me.

I think I could create a data-entry screen using HTML, CSS, and JavaScript that could rival 5250 performance and keyboard support, but must admit that it would take a lot more work than using DSPF DDS.  On the other hand, if I were to go to the trouble, I'd probably create a generic JavaScript library that could be applied to any browser-based data-entry form.

Nathan.




--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.