RE: RPG is Dead? Say it aint so!

["Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>]

> From: albartell
>
> > As to debugging, as I said to Aaron you're as likely to have to debug the
> inner EGL code as you are to debug the inner working of CGIDEV2.
>
> I am not talking about debugging the EGL framework (which is semi
> equivalent
> to debugging CGIDEV2), I am talking about debugging the code EGL generates
> (which is a component the CGIDEV2 doesn't have - for better or worse).

Okay, gotcha.  But you do realize that the "generated code" is really just
EGL, right?  In general there is very little code.  When you create a page,
EGL generates a template and then you fill in the code (just like the
various .NET languages).  The code for simple inquiries is typically just a
few lines using a very BASIC-like syntax.

You might really want to look at a couple of my articles:

http://www.mcpressonline.com/mc?.6b36d2b1

http://www.mcpressonline.com/mc?.6b3a121c

http://www.mcpressonline.com/mc?.6b3a3717

http://www.mcpressonline.com/mc?.6b3cd66b

 

> What does that mean?  To me it says that yes EGL does shield you from
> HTML/CSS/Javascript for the most part, but again, you will be debugging it
> sometimes, and CGIDEV2 simply makes you take the plunge into
> HTML/CSS/Javascript right away.

Well, I suppose.  But it's the same with DreamWeaver - it's a WYSIWYG editor
that makes it a lot easier to do what you could do yourself with a test
editor.  And while there are those who love text editors for HTML coding,
the folks who don't want to learn every tag are happy to use a tool.

EGL is a tool for generating applications quickly.  It's easier than RPG-CGI
and easier than JSP.  And with version 7, it generates rich clients as well
as browser apps, which is something none of the approaches provides easily.

Joe