This isn't true.
Sorry, what isn't true?
Profound UI is not based on applet technology
I've never implied nor said that it was "applet technology". This is the
second time you've lambasted me on this list while implying that the only
definition of "applet" is "java applet technology". Please google "define
applet". The first entry that comes up is:
"a very small application, especially a utility program performing one or a
few simple functions."
That definition accurately describes the JavaScript "client" which is
downloaded to the browser when a Profound UI session starts. It's a
JavaScript file, but I believe the most accurate way to label it is
"applet" or "client". It's not a "framework" - it doesn't expose an API for
developers.
Ironically the size of the JavaScript file (approximately 750K) is about
the same size as the TN5250J client which I use, which IS A JAVA APPLET.
And the behavior implemented in the Profound UI client is very similar to
that of the TN5250J client. It "interprets" a "data stream" downloaded from
IBM i and "renders" it on the screen. And similarly generates a data stream
when forwarding requests to the server.
If you examine the data streams which are passed back and forth between the
"client" and "server", you see that they have a lot of properties which are
comparable to a 5250 data stream, including the fixed location and size of
screen elements, both input and output.
it uses normal modern web technologies such as HTML5, CSS, and JavaScript.
Obviously, it runs in a browser after all.
It uses the SPA paradigm, which is very popular in web applications today.
There you go aligning Profound UI with a popular technology. Unfortunately,
the comparison is shallow. You make a good point in the sense that the
Profound UI client runs in a single web page. But the alignment with the
SPA paradigm ends there.
I don't understand why Nathan is saying these things? Maybe he works with
one of our competitors?
Don't take it personally. I've said a lot of nice things about you and
Profound Logic over a period of many years. A competitor? Perhaps in the
sense that I earn a living by developing and hosting IBM i web applications
- also developing IBM i web frameworks.
Profound UI is a suite of several tools with many different capabilities.
One of the tools, named Genie, provides 5250 emulation and refacing in a
browser interface. So, it does do terminal emulation for that reason. The
other tools in the suite do not do terminal emulation at all.
Sorry, I see more similarities between a screen-scraper like Genie and the
open-access handler which is used with the Visual Designer, than
distinctions. They both follow the traditional display file paradigm of
writing "records" and reading them.
Profound UI is not "constrained" at all.
Sorry, I disagree with that as well. "writing" and "reading" display file
records is a constrained paradigm in comparison to designing and writing
your own HTML, JavaScript, CSS, and IBM i "servers" which respond to any
type of event from whatever client you may write from scratch.
But please don't listen to Nathan. He is not a Profound UI customer, and
none of the things he says here are true. Frankly, he has absolutely no
business answering questions about Profound UI, as he clearly knows nothing
about it.
Now that's just harsh, and personal. How many times have you written about
or compared various web or application interfaces, frameworks, or platforms?
midrange.com
