WFL/DCP SPO: Difference between revisions
From Cibernética Americana
Jump to navigationJump to search
No edit summary |
|||
| (43 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 | == Current state of Smalltalk platforms == | ||
<blockquote style="color:black;background-color:white;"><blockquote> | <blockquote style="color:black;background-color:white;"><blockquote> | ||
<br> | <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> | |||
<div style="float: right;"> | |||
</blockquote></blockquote> | |||
== 4720 Story == | == 4720 Story == | ||
| Line 21: | 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, 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> | <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 | <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%> | style="width: 200px;" src=https://meansofproduction.biz/images/SPO-JS-tn.png></blockquote></td><td width=50%> | ||
| Line 39: | Line 37: | ||
</ul><div style="width: 950px;"> | </ul><div style="width: 950px;"> | ||
<blockquote> | <blockquote> | ||
"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 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. | "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> | ||
