I did a lot of work with panel/skeleton/tables/etc and productivity app development at IBM in the 70s and 80s, both on the original ISPF and later on ISPF/PDF.
SPFLite operates with essentially just two display panels - one for FM and one for everything else.
The only difference between the two is the top few lines.
The remainder of both screens is a programmatically populated area, consisting of a short data entry column for line commands/numbers followed by a line area.
SPFLite is PC based, so the concept of entry/no-entry fields is easily managed by allowing where you can type and where you can not type.
By contrast ISPF is 3270 ATTN event-based, relied on a relatively dumb control unit, and field attributes and positioning were awkward to program directly.
IBM's initial product called ISPF (Interactive Structured Programming Facility, I think!) consisted of a "display component" specifically designed for 3270s to support the initial 7-or-so Options of Browse, Edit, Utilities, etc.
Given the complexity of 3270 programming and a user population who wanted to develop bespoke productivity extensions or even applications, there was a sound commercial incentive to improve/extend ISPF.
So IBM separated the functional aspects of the product into two parts:
- an enhanced 'panel' component, still called ISPF (renamed Interactive System Productivity Facility), and
- the familiar Browse/Edit/Utility, etc part, renamed PDF (Program Development Facility), which used the new ISPF as the 'display component'.
ISPF offered CALL-access (ISPEXEC) to built-in capabilities like 3270 Display Mgmt, Table Mgmt, File Tailoring, Library Mgmt, Variable pool Mgmt, etc.
All PDF capabilities could similarly be acessed via ISREDIT
This new structure greatly simplified development of bespoke applications, an attractive idea given the 3270 platform.
So am I interested in SPFLite handling of Panels?
No. I'm sure it could be done, but I see no return on the significant investment.
Most SPFLite users hail from the MVS/z-Series environment.
Even if the new 'display layer' were as comprehensive as ISPF, it would also need to be an 'ISPF clone' so current and ex-mainframe users can immediately feel familiar with it.
All that said, I do have some home-written Utility programs that generate reports.
And I do present those reports via SPFLITE because the capabilities of AUTO highlighting combined with IMACRO highliting makes them much easier to read.
The reports even use 2-byte "attribute" chars that inform the IMACRO high-lighting. (yes, I am that sad!)
So I am (kind of) using SPFLite as a presentation layer.