× 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.



From: Joe Pluta
I disagree a bit with Nathan about throwing out your existing RPG
code.

Let me qualify that a bit. You make a good point about shops that may have already moved to writing ILE procedures - I get the impression that most RPG shops haven't, but I failed to make that point.

If you categorize existing code for interactive applications as follows:

1. User interface definition.
2. User Interface I/O.
3. Flow control - how programs respond to user events.
4. Navigation and state transitions from one screen to the next (or whatever).
--
5. Database definition.
6. Database I/O.
--
7. Data validation & business rules.


I suspect that categories 1-4 contain the majority of existing code, which is what I'd tend to replace outright because it would be very unlikely for any of it to fit within my Web 2.0 UI & RPG models. We also see the problem where so much of it is mixed in a monolith - so that it's too hard to work with.

Regarding categories 5-6, I tend to generate most of that code from metadata, and encapsulate it into modules. Extracting it from a monolith may not be worth the time.

Regarding category 7, that's the kind of stuff I'd like to keep, particularly if it were encapsulated in procedures.

-Nathan.





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.