WFL/DCP SPO: Difference between revisions
From Cibernética Americana
Jump to navigationJump to search
| (128 intermediate revisions by the same user not shown) | |||
| Line 2: | Line 2: | ||
<html><div style="background-color: gray;color: white;"></html> | <html><div style="background-color: gray;color: white;"></html> | ||
<blockquote> | <blockquote> | ||
== | == Current state of Smalltalk platforms == | ||
<blockquote style="color:black;background-color:white;"><blockquote> | |||
<br> | |||
*Squeak6.0 Desktop <blockquote>This is the current level used by the DGUI Project which will load in a current Squeak 6 with Squot from the source Squit repo. Desktop is the reference SPO environment, the web version is a convenience for DCMS users. Since the desktop version can run in a desktop sharing session in a browser, or from an MCP node via vnc, it is the preferred version there too.</blockquote><div style="color: yellow;background-color:black;float: right;"> [https://ns.meansofproduction.biz/SPO/run <span style="color: cyan;">WEBSPO</span>] is set as the home panel for DCMS devops users.</div> | |||
*The SqueakJS SPO subset (WEBSPO) runs in browsers from images on a browser disk. | |||
<br>On fileIn, a SPO level presumes a level of squeakmap, monticello, etc. but thereafter generally diverges in its internal squit repo. | |||
Whether in a browser or on a desktop a SPO must be served from a node of a MCP for the full set of ops. | |||
<br></blockquote></blockquote> | |||
== 4720 Story == | |||
My first professional Smalltalk use was in 1985/6 and the <span class=plainlinks>[https://juan.ai-integration.biz/everything/index.pl?node=XSQL <span style="color: pink;">last big app</span>]</span> before the DGUI was in the mid nineties. '''SPO''' was/is a term for the system operator console in Burroughs/Unisys MCP. Similarly WFL is Work Flow Language, the MCP Job Control Language and a future intent for the domain space Master Control Program. DCP is domain control program which is novel to domain space. | |||
<br><br> | <br><br> | ||
| Line 10: | Line 19: | ||
The SPO would be associated with a particular Operator Display Terminal (ODT), by assignment in the NDL (Network Definition Language) sources for the machine controlled.<br/><br/>The TD series (classic TD830 shown) were typically used in the seventies and early eighties. The "dumb" terminal is actually in the keyboard. I also used an "SR" station type with a more programmable microprocessor introduced after the TD. | The SPO would be associated with a particular Operator Display Terminal (ODT), by assignment in the NDL (Network Definition Language) sources for the machine controlled.<br/><br/>The TD series (classic TD830 shown) were typically used in the seventies and early eighties. The "dumb" terminal is actually in the keyboard. I also used an "SR" station type with a more programmable microprocessor introduced after the TD. | ||
</td></tr> | </td></tr> | ||
<tr><td colspan=3>This image shows a lot of reverse video, they were normally white text on black. I believe they also could be configured like a contemporary IBM 3270 for "greenscreen" green on black or amber. There also was an ET series (shown below), a more modern version of the TD monitor (shown above).</td></tr> | <tr><td colspan=3>This image shows a lot of reverse video, they were normally white text on black. I believe they also could be configured like a contemporary IBM 3270 for "greenscreen" green on black or amber. There also was an ET series (shown below), a more modern version of the TD monitor (shown above, an 800 I believe). My desk had an SR model iirc, unlike these two.</td></tr> | ||
</table> | |||
<table><tr><td align=left width=50%><blockquote><b> Linux, Mac, or Windows desktop is reference version (DGUI)<br>Desktop and web SPO loaders are available from your DCMS account.</b><br><br> | |||
<a title="Zoom into current snapshot" href=https://meansofproduction.biz/images/SPO-JS.png><img | |||
style="width: 200px;" src=https://meansofproduction.biz/images/SPO-JS-tn.png></blockquote></td><td width=50%> | |||
<a title="Zoom into 4714 snapshot" href=https://meansofproduction.biz/images/SPO.jpg><img src=https://meansofproduction.biz/images/SPO-tn.jpg></a> | |||
</a></tr> | |||
</table> | </table> | ||
</html> | </html> | ||
<br><br> | <br><br> | ||
In my reimagined context, | In my reimagined context, SPO is just the smalltalk code which is developed to run in Squeak 5.3 or later from desktop or web in support of domain space. | ||
<ul> | <ul><span class=plainlinks> | ||
<li>FileList adapted for MCP file system model</li> | <li>[https://meansofproduction.biz/images/MCPLoadState.png <span style="color: pink;">MCP console </span>] (Unisys, conceptual inspiration).</li> | ||
<li>FileList proven/adapted for MCP file system model</li> | |||
<li>CommandShell adapted for [https://meansofproduction.biz/mcplaunch.html <span style="color: pink;">mcpcms</span>].</li> | <li>CommandShell adapted for [https://meansofproduction.biz/mcplaunch.html <span style="color: pink;">mcpcms</span>].</li> | ||
<li> | <li>[https://ac.ai-integration.biz/?startPane=AC <span style="color: pink;">DCP Console</span>] / KEE SPA, morphic is reference version (redvant version linked).</li></span> | ||
</ul><div style="width: 950px;"> | </ul><div style="width: 950px;"> | ||
<blockquote> | <blockquote> | ||
"DGUI" could be somewhat misleading, since here "domain" refers only to the | "DGUI" could be somewhat misleading, since here "domain" refers only to the GUI aspect of domain space as such. In fact. anything that could run on a node could produce a native GUI or web UI. The Domains GUI prefers Smalltalk on aesthetic as well as practical grounds but [[redvant|<span style="color: pink;">redvant</span>]] is also used and many embedded systems have their own none of which are what is meant by 'DGUI' in the narrow sense of this page. | ||
</blockquote></div> | </blockquote></div> | ||
== "Supervisory Print Out" == | == "Supervisory Print Out" == | ||
In the original [[:en:Master Control Program|<span style="color: pink;">MCP</span>]] based systems one or more consoles could function as the "SPO", the system operator interface. Originally it stood for "Supervisory Print Out" in the early MCP (presumably B5000 or possibly earlier). | In the original [[:en:Master Control Program|<span style="color: pink;">MCP</span>]] based systems one or more consoles could function as the "SPO", the system operator interface. Originally it stood for "Supervisory Print Out" in the early MCP (presumably B5000 or possibly earlier). The ATTACHSPOQ DCALGOL function determines the current SPO. | ||
< | <br><br> | ||
In my homage it has become simply "SPO" ('spoh') for DCP/MCP, the set of squeak sources as described above as a UI for the dominion control program in the style of the Burroughs MCP. BTW, this is a good place to point out the diff between "Burroughs MCP", "Unisys MCP", and just "MCP". The second is the product marketed by Unisys which until recently I had not had hands on since my use of it as systems programmer in the 80s but which is now available as "MCP Express" that runs under Windows. The last is my invention which is no more than inspired by Burroughs MCP 4, the version of the Algol OS with which I had paid experience than 18/19 the current one in 2020/4718. | |||
In my homage it has become simply "SPO" ( | |||
== Links== | == Links== | ||
Latest revision as of 22:16, 24 March 2023
Current state of Smalltalk platforms
- Squeak6.0 Desktop
This is the current level used by the DGUI Project which will load in a current Squeak 6 with Squot from the source Squit repo. Desktop is the reference SPO environment, the web version is a convenience for DCMS users. Since the desktop version can run in a desktop sharing session in a browser, or from an MCP node via vnc, it is the preferred version there too.
WEBSPO is set as the home panel for DCMS devops users.- The SqueakJS SPO subset (WEBSPO) runs in browsers from images on a browser disk.
On fileIn, a SPO level presumes a level of squeakmap, monticello, etc. but thereafter generally diverges in its internal squit repo. Whether in a browser or on a desktop a SPO must be served from a node of a MCP for the full set of ops.
4720 Story
My first professional Smalltalk use was in 1985/6 and the last big app before the DGUI was in the mid nineties. SPO was/is a term for the system operator console in Burroughs/Unisys MCP. Similarly WFL is Work Flow Language, the MCP Job Control Language and a future intent for the domain space Master Control Program. DCP is domain control program which is novel to domain space.
The SPO would be associated with a particular Operator Display Terminal (ODT), by assignment in the NDL (Network Definition Language) sources for the machine controlled.
The TD series (classic TD830 shown) were typically used in the seventies and early eighties. The "dumb" terminal is actually in the keyboard. I also used an "SR" station type with a more programmable microprocessor introduced after the TD.This image shows a lot of reverse video, they were normally white text on black. I believe they also could be configured like a contemporary IBM 3270 for "greenscreen" green on black or amber. There also was an ET series (shown below), a more modern version of the TD monitor (shown above, an 800 I believe). My desk had an SR model iirc, unlike these two.
Linux, Mac, or Windows desktop is reference version (DGUI)
Desktop and web SPO loaders are available from your DCMS account.
In my reimagined context, SPO is just the smalltalk code which is developed to run in Squeak 5.3 or later from desktop or web in support of domain space.
- MCP console (Unisys, conceptual inspiration).
- FileList proven/adapted for MCP file system model
- CommandShell adapted for mcpcms.
- DCP Console / KEE SPA, morphic is reference version (redvant version linked).
"DGUI" could be somewhat misleading, since here "domain" refers only to the GUI aspect of domain space as such. In fact. anything that could run on a node could produce a native GUI or web UI. The Domains GUI prefers Smalltalk on aesthetic as well as practical grounds but redvant is also used and many embedded systems have their own none of which are what is meant by 'DGUI' in the narrow sense of this page.
"Supervisory Print Out"
In the original MCP based systems one or more consoles could function as the "SPO", the system operator interface. Originally it stood for "Supervisory Print Out" in the early MCP (presumably B5000 or possibly earlier). The ATTACHSPOQ DCALGOL function determines the current SPO.
In my homage it has become simply "SPO" ('spoh') for DCP/MCP, the set of squeak sources as described above as a UI for the dominion control program in the style of the Burroughs MCP. BTW, this is a good place to point out the diff between "Burroughs MCP", "Unisys MCP", and just "MCP". The second is the product marketed by Unisys which until recently I had not had hands on since my use of it as systems programmer in the 80s but which is now available as "MCP Express" that runs under Windows. The last is my invention which is no more than inspired by Burroughs MCP 4, the version of the Algol OS with which I had paid experience than 18/19 the current one in 2020/4718.Links
- Burroughs Large Systems (external)
- Burroughs MCP Architecture (internal)
- CANDE
- Squeak
- WFL
