Yes,
You don't need to access the iseries, but you can if you wish. I call
rpg/free pgms to build my work files, then use egl to display on web page.
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On
Behalf Of Dave Odom
Sent: Wednesday, January 02, 2008 8:01 PM
To: 'Web Enabling the AS400 / iSeries'
Subject: Re: [WEB400] EGL in 15 Minutes
Joe,
Do I understand correctly that one can use EGL to build Web apps without any
tie to any legacy i5 language like RPG?
Thanks,
Dave
"Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx> 1/2/2008 11:18 >>>
I just wanted to let everyone know that my article on EGL, "The Business of
EGL", is available at the following URL:
http://www.ibmsystemsmag.com/i5/developer/18728p2.aspx
In it I document, with screen shots, the 15 minutes I spent developing two
complete applications over System i data - one CRUD and one query (with
business graphics) - using EGL. I'm not trying to say these programs are
production-ready applications, but they are complete, functioning skeletons
that bring System i data to the web in literally minutes and can be used as
a basis for RAD sessions with users, something we've been missing in the
System i world.
You might say that putting System i data in a browser makes EGL little more
than a web application framework like so many others out there, and if this
is as far as EGL went that would indeed be true. The beauty of EGL as
opposed to any other approach is that the next step, integrating with RPG
business logic, is built into the system from the ground up. Complex data
objects can be passed between EGL and RPG with a single call instruction,
making multi-tiered architectures almost trivial to implement.
I've cross-posted this in three forums. If you have questions about EGL and
RPG interaction and the language in general (prerequisites and so on),
Midrange-L is probably the best place to ask about it.
If you want to know more specifically about the web UI capabilities, which
for now are primarily limited to JSF but which will be greatly expanded in
the next (and following) releases, I'd probably suggest WEB400-L.
And finally, issues relating to packaging and integration with WDSC belong
in WDSCI-L.
Thanks, and Happy New Year!
Joe
midrange.com
