×
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.
Nathan Andelin wrote:
Joe,
Why did the discussion change from ideas and information to
"you...you...you..." 23 times. This is not about "me".
Oh poo, Nathan. This is just downright silly. The reason your name is
attached to my challenging of your ideas ideas is because they're YOUR
IDEAS. This is your solution, which you freely presented as an
alternative technology. I'm simply challenging your assertion that it's
as easy as EGL.
If Brad presents RPG-CGI in whatever flavor he likes, I'll direct the
questions at him.
I'm tired - very, very tired - of the lack of intellectual rigor in the
IBM i community when it comes to web enabling. As a technology, RPG-CGI
is a poor choice, *unless* your only tool is the RPG hammer. Tagging is
a second-rate solution - JSP does it better, and it's still bad. There
is no context, and no tooling to support it. There is no programmatic
binding of data fields between the application code and the UI;
everything is manual. Not to mention, as soon as you manually insert
tags, your WYSIWYG tools barf. This is a bad technology.
(By the way, there is at least one framework that supports
"flow-through" or "invisible" tags, and so allows most standard WYSIWYG
editors to work on tagged source. RPG-CGI is not one of those. See
Tapestry for an example of tagging done as well as can be done.)
JSF gets it closer. Not 100%, but much closer. And the JSF bindings
are included in the tooling. EGL and the RBD tooling are better,
easier, faster and more efficient than any RPG-CGI tooling you can
name. It's that simple.
And if you want to disagree with me, that's cool, too. Just be prepared
to back it up.
Joe
As an Amazon Associate we earn from qualifying purchases.