Re: Future of RPG

Glenn

I have little experience with actually, formally, consciously separating presentation from business logic - but this Open Access initiative seems like it could support that concept nicely - same code in RPG can be pointed at one of several presentation devices and still work - business logic does still have to request presentation, right? Am I off base in my understanding?

Vern

On 7/29/2010 7:08 AM, Glenn Hopwood wrote:

On 7/28/2010 2:31 PM, THarteau@xxxxxxxxxxxxxxxxxx wrote:

It was done in green screen because we are missing the information
on how to make a GUI front end work with RPG. How can you do this
efficiently with RPG doing most of the work? I have taken a couple of
hour long sessions on PHP& EGL, but how does the data go between the
screen& the program? I understand the syntax, but the implementation is
what I have a problem with, and don't have the time to figure out. How
can passing all the fields (20+) through the IFS or something else be as
fast as a green screen with subfiles? I haven't looked extensively, but I
have not seen step by step instructions on how to make a GUI screen work
with RPG. I have seen how to write the screen, how to write the program,
but how is the information passed back and forth? This may not make a lot
of sense, but this would have been a perfect project to use new
techniques, but I did not see a fast way to get it up and running.

The method of data transport depends on what solution you decide to use.

I know this is an RPG list, but... For your first couple of attempts why
even try to pass the data to an RPG program? Do you have logic already
written that you want to reuse? If you're writing a new maint screen why
not do all of the code in whatever presentation language you choose?

Ideally you want your presentation separated from your business logic
but why not step up to that slowly? You won't be any worse off then you
already are...

Glenn