RE: A design philosophy question -- RPG400-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: RE: A design philosophy question
From: "McBride, Lane (Artco)" <lmcbride@xxxxxxxxxxxxxxx>
Date: Mon, 30 Sep 2002 12:25:14 -0500
List-archive: <http://archive.midrange.com/rpg400-l/>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: RPG programming on the AS400 / iSeries <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/cgi-bin/listinfo/rpg400-l>,<mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/rpg400-l>,<mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

>I'd love to hear discussion on this, but IMO option one is the best choice.
>That then leaves my original three options:
>
>1. Individual programs
>2. Modules bound by copy
>3. Modules in service programs

I think option 3 is the way to approach it.  If MVC architecture is used to
assemble the "view" components with the calling RPG ("model") this makes the
program and DDS more flexible.  That way you could assemble your panels
using windows in DDS or you could port the same application to CGI just as
easily.

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.