Our company has recently tried to steer away from using multiple displays.
We've found that the more displays you have to manage in a program, the
longer the program becomes and more complex it ends up being. Ever try to
read a program that uses 6 different displays, all with subfiles? Nasty!
(Especially if all of the fields are named slightly different, because none
of the files are prefixed!).
That said, we do still on occasion keep multiple display files together. An
example might be a maintenance program where you have a couple of add /
change windows to bring up. When possible, we split into one display per
program. More modular that way too!
Carmen
-----Original Message-----
From: Thompson, Glenn [mailto:gthompson@xxxxxxxxxxxxx]
Sent: Tuesday, October 30, 2007 9:37 AM
To: RPG programming on the AS400 / iSeries
Subject: Multiple Displays vs One Display
I have an opinion oriented question. I have noticed in our shop that
many programs use multiple displays within one program. What is the
prevailing wisdom of many displays in a program versus one program/one
display?
Glenn Thompson
Senior Analyst
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.