Re: Multiple Displays vs One Display

[Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>]

This is an interesting thread.  I've never hard of this "one screen / 
one module" recommendation before.  I'm having a hard time understanding 
why you'd do this...

All of the recommendations I've seen involve separating the display 
logic from the business logic -- usually using an MVC pattern.  I've 
never heard of separating the display logic from other display logic. I 
don't understand the advantages of separating each screen from the other 
ones.

Can you please provide links to where you saw these recommendations? 
Preferably, a link to an article that really explains the premise of 
this technique?

Thanks


Wilt, Charles wrote:
> Now-a-days, I think most the experts recommend one screen per
> module/program.  While not an expert, that's what I'd recommend also
> :)
>
> Tends to lead to more modular programming.  Maintenance is easier as
> you don't have to worry about accidentally changing another screens
> behavior.
>
> Also makes it easy to call a particular screen from someplace else.