And then you hand that off to the EGL programmer. That person can write
thick client, rich client, thin client, it don't matter. They can call
your program directly, or they can use a few lines of EGL to expose it
as a service to others. But you the RPG programmer never have to touch
the "webby" stuff. Can't say that about RPG-CGI.


Not never, but it can be VERY miminal.

Have the "webby" folks do the templates. A small learning curve on how they
work, and bingo. Just tell me the names of the sections and replacement
variables and I'll code the RPG.

I've done it that way before. I've also done it where I build a basic
template and they add whatever they want (stylesheets, images, etc).

Then again, I like to get my hands dirty with the webby folks so I can learn
more and more. although, with today's WYSIWYG tools, they produce some
pretty awful looking code HTML/JavaScript/CSS.. *shudder*

for one of the examples before (the insurance one) that I posted, that's
exactly what we did. I wrote the CGI, Aaron's "webby" folks at his place
did the beautification. That was almost a perfect example of having the
right skillsets involved to produce a great application.

Brad
www.bvstools.com


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.