You have heard my name before, haven't you?
Scott,
Thanks for the reply. Of course I know who you are. Seems odd that you'd
ask. I wasn't preaching to the choir. My posts are for everyone. Sorry if
it seemed like me singling you out. I was suggesting that shops which are
gaining greater awareness of the technical debt in their legacy systems are
more likely to look at web application architectures other than "display
files" and OA interfaces.
Regarding "applets", consider definitions from www.dictionary.com:
"a small application program that can be called up for use while working in
another application."
"a computer program that runs within a page on the Internet."
"A small computer program that has limited features, requires limited
memory resources, and is designed to be downloaded from the Internet to run
on a webpage."
I think "Applet" is a better term than "JavaScript Framework" because the
latter implies a library of functions for JavaScript programmers; like
JQuery.
Your point about it being written in JavaScript rather than Java is well
taken. I'll try to remember to make that distinction in the future.
The main point is that it is an application which performs a service which
is comparable to a 5250 emulator; runs in a web page, transforms meta data
streams received from an OA handler into visual elements, forwards data
changes and events to the server which occur in the client. The
similarities to 5250 are remarkable. Its noteworthy that Profound "owns"
the interface rather than IBM, and can adapt it.
Thanks for the information about <iframe> support in the Profound UI Visual
Designer. I just note that each <iframe> references a separate Profound UI
"JOB", or other external resource, and not belabor the point.
Regarding "Responsive UI Design", I would suggest viewing the link I posted
earlier, using a cell phone, tablet, and desktop screen. The layout
automatically adapts to the size of the screen. Looks better on a cell
phone than on a big screen monitor in my opinion.
http://www.radile.com:9220/rdweb/phones/phonelist.html
You don't need to be a skilled UI designer for that. The "list" is
generated from this HTML template:
http://www.radile.com:9220/rdweb/phones/phones.html
The "detail" is generated from this:
http://www.radile.com:9220/rdweb/phones/phone.html
I could do more to improve the appearance. But that was not my focus. I
carelessly threw the HTML together based on the layout of some JSON objects
which I downloaded from the Angular JS web site.
The point is that one may prefer using that approach, rather than designing
separate "display files" for different screen sizes.
midrange.com
