Just to clarify....
ProfoundUI applications are SPAs. Our framework dynamically renders each screen using the metadata send from the handler. Technically our products are one big SPA.
Also, you can build responsive applications using our toolset as well.
UI modernization of existing applications is a starting point. It allows our customers to move existing applications forward with confidence. They soon find they can also build new applications in a more modern and modular fashion, as you describe, but they can continue to use our tooling for UI design and even our handler to handle interfacing with the UI.
Not pitching our products here, but since they were under discussion, I felt clarification was warranted.
Brian May
Solutions Architect
Profound Logic Software
http://www.profoundlogic.com
937-439-7925 Phone
877-224-7768 Toll Free
The IBM i Modernization Experts
www.profoundlogic.com
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Nathan Andelin
Sent: Tuesday, June 09, 2015 9:58 AM
To: Midrange Systems Technical Discussion
Subject: Re: 'green screen' not sellable --> WE(?) are the problem
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.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
http://archive.midrange.com/midrange-l.
midrange.com
