Something like Profound UI's tooling seems ideal - no change needed to the
RPG code at all
Nice endorsement, Vern. I agree that Profound has good tools for IBM i
application development and good people supporting them. But I think it is
important to note that there are trade-offs associated with every tool-set
and "modernization" methodology.
Rather than "no change needed to the RPG code at all", a higher priority
might actually be to refactor some code, eliminate some, and replace some
to fit within an application architecture which is more maintainable over
the long run.
Another priority might be to provide a UI which automatically adapts to all
classes of devices (cell phones, tablets, laptops, desktops) rather than
separate "display files" and different applications for different sized
screens. This strategy is known as "responsive UI design".
I like to use <iframe> elements, but having multiple frames in applications
doesn't fit with an Open Access architecture. I advocate for "single page
applications", where each "page" may be divided into many "containers",
where each container has a different layout and different data; where the
content is dynamically "injected" into each container as needed over the
lifespan of the application.
With browser caching as an option, it is possible for developers to decide
whether to refresh a screen by making a server "request", or to just use
what's available in cache.
If green-screens are not sell-able, what makes HTML renderings of the same
applications more so?
I agree that leveraging existing code-bases and skill-sets has value;
hosting applications on IBM i has value. But to fully utilize browser
capabilities, people need to learn to code differently.
midrange.com
