WFL/DCP SPO: Difference between revisions
From Cibernética Americana
Jump to navigationJump to search
| (51 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> | ||
== | == Domain Graphical User Interface (DGUI) == | ||
<blockquote style="color:black;background-color:white;"><blockquote> | <blockquote style="color:black;background-color:white;"><blockquote> | ||
<br> | <br> | ||
* | * Full Function <blockquote>Squeak 6 is the version used as the direct control cell of DCP/MCP and this is the reference and only complete DGUI. The code can run on Mac and Windows but I only support those platforms via remote desktop to a linux vm/image. FileOut sources to port to other st setups.</blockquote> | ||
* | * Limited Function | ||
< | **A SqueakJS SPO (WEBSPO) runs from browsers ...<blockquote> .. as a convenience for DevOps users. Originally I thought missing networking functionality was just backlogged but came to understand the inherent limitations of js vm are not such as can be reasonably addressed and so this must be kept in mind in using this subset which is good enough effort subject to these limitations.</blockquote><br><div style="color: yellow;background-color:black;float: right;position:relative;top:-20px;"> [https://ns2.meansofproduction.biz/SPO/run <span style="color: cyan;">WEBSPO</span>] is selectable as a home panel view on devops1.sameboat.</div> | ||
**Pharo <blockquote>As in the squeakjs case (vm reasons) and for additional ones specific to it, Pharo support by me is limited to a first pass on fileIn of the above sources. In principle, the Pharo version should be intermediate between the Squeak and squeakjs ones but I dont intend to personally make it so.</blockquote> | |||
< | |||
On fileIn, a SPO level presumes a level of squeakmap, monticello, etc. but thereafter generally diverges in its internal git repo.<br> | |||
WEBSPO actually just has limited ODT functionality and cannot control a DCP.<br><br> | |||
</blockquote></blockquote> | |||
=== vs. DS G === | |||
Altho they have obvious superficial similarities, the visual programming paradigm and smalltalk are distinct, historically and in this novel. DS G is developed from the start based on node red building bottom up with DCP/MCP custom nodes and other contrib flows like the excellent Xstate smxstate. Smalltalk is about a decade older that G (LabView) FWIW. A G lang implies a façade over some generated backend and that's kinda the opposite of st which generates bytecodes for a vm tightly bound to the lang. It is also less of a general purposes lang with its control system and instrumentation focus. | |||
<hr> | |||
<small>Rest of this page unmaintained background on the SPO concept, in a running image the current code should be consulted in a Browser under the DomainSpace category .</small> | |||
== 4723 Update == | |||
Google AI suggests in response to the prompt "what does SPO mean in an ALGOL context?" that in addition to system console it means System Primary Output. SFAIK, Supervisory Print Out is the actual etymology but like what gemini confabulated better. | |||
== 4720 Story == | == 4720 Story == | ||
| Line 19: | Line 34: | ||
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, an 800 I believe).</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> | ||
<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> | <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> | ||
| Line 46: | Line 61: | ||
== Links== | == Links== | ||
*<span class=plainlinks>[https://meansofproduction.biz/pub/SPO-ConsoleUG.pdf <span style="color: pink;">2003 Common MCP 0S2220 Unix SPO Guide</span>]</span> | |||
*[[:en:Burroughs large systems|<span style="color: pink;">Burroughs Large Systems</span>]] (external) | *[[:en:Burroughs large systems|<span style="color: pink;">Burroughs Large Systems</span>]] (external) | ||
*[[Burroughs MCP Architecture|<span style="color: pink;">Burroughs MCP Architecture</span>]] (internal) | *[[Burroughs MCP Architecture|<span style="color: pink;">Burroughs MCP Architecture</span>]] (internal) | ||
