Re: 'green screen' not sellable --> WE(?) are the problem

Scott,

Thanks for the reply. I understand the business case for a UI
"modernization" strategy which is based on display files and related op
codes. That's a nice niche for Profound to be in. However, I believe
there's also a business case for a reduce/refactor/rewrite/replace
strategy, which may also be supplemented by "utilities" which eliminate a
lot of old code. Monolithic applications tend to generate a lot of
technical debt over time that makes them less "sell-able", much harder to
maintain, and ripe for replacement.

Regarding the <iframe> issue, could you clarify whether <iframes> are a
component on the Profound UI screen designer? If not, then why not? I can
see developers embedding <iframe>s in pages, including one or more frames
hosting separate Profound UI "sessions". But I don't see how a display file
and op code paradigm could handle requests from events which may be
occurring in multiple <iframe>s simultaneously. I could see having frames
handled by separate "applications" and "sessions". Was that what you meant
by having customers doing that all of the time?

I reviewed what I wrote previously. I probably confused people by talking
about <iframe>s and SPA "containers" in the same paragraph. They are very
different architectures and interfaces. Maybe I'll say more about SPA
containers later.