|
>There is an answer. It's a staged approach: >1. Separate UI and business logic Hi Joe! This first step is a doosy! Let me start by saying that I am a complete novice when it comes to the Brave New eWorld, so rather than arguing, I am searching for answers... I hope I come across that way! If I have a 3 program Classic application (sounds better than "Legacy"): Enter/validate customer number (PGM1) Enter/validate order header (PGM2) Enter/validate order details (PGM3) Separating the UI from each program is easy enough - I've used the data queue method before when working with asynch devices like telephone switches. Separating the UI from the _application_ is somewhat harder, because there is an implied relationship between the panels that PGM1 displays and those that PGM2 displays. I suppose (typing whilst I think - ever dangerous!) that I could do the program-UI decoupling as step 1a, and then write my own single panel UI that "knows" about the individual RPG programs, and parses out the multiple buffers from RPG to the single "buffer" of the new UI. Step 1b. Buck
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.