|
Gary, 5250 isn't an option - we'd have to add 400 interactive users to the less than 50 we have now. We have 'some' in-house expertise. I've done a lot of RPG-CGI stuff, and a little domino developement, and we have 2 other guys who're a little better at the domino stuff than me. I'm getting a lot better at ILE concepts, and I'm pretty decent with html and javascript too. I see the subject of separating business logic from presentation on this list a lot, and i'm convinced this is a good idea, but I'm just a little fuzzy on exactly how to achieve this. I would love to see a best practices discussion on this, and maybe a small example of how it's best done. Rick -------Original Message------------ Rick, Given you've charted the workflow it now seems you are at stage where data elements can be mapped to a database (existing or to be created). Once that is done you can decide on user interface - GUI or green screen. With GUI there is the choice of browser or writing your own fat client. If you don't have the in-house expertise, or money to experiment some, GUI is probably a phase 2 project. With a green screen approach you get something in place rather quickly. The remote sites would need an emulator though. It can always be GUIized at a later time. Separating business logic and database updating from of presentation logic will start you on the road to having the application ready for your GUI project.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.