|
This is an interesting thread. I've never hard of this "one screen /understanding
one module" recommendation before. I'm having a hard time
why you'd do this...I
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.
don't understand the advantages of separating each screen from theother
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.
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.