|
> A change in the user interface should not require a > change in the program. > For example, an RPG program should have NO imbedded HTML, > XML, or > JavaScript. I agree here to a point. But there's nothing wrong with using RPG as the "display layer" of the application. It's really more similar to Perl in this case. There's no rule that says different. You should seperate business logic from display logic, but this does not mean that each of these layers needs to be different scripting/programming language. I think people are assuming that using a CGI programming language like RPG that everything is done in "one program". While this is the case with applications (no matter the language used, be it Java, Net.Data, RPG, Perl, etc..) it is not always the case. It's too easy to say how you should do things than actually doing it. So I don't let posts like this off too easy. :) I'd like to hear an example of two things. 1. A change in the user interface that requires a change in a CGI program/script 2. How using your techniques (specific example would be ideal) makes this change in the program/script not needed Brad www.bvstools.com
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.