WFL/DCP SPO: Difference between revisions
From Cibernética Americana
Jump to navigationJump to search
| Line 6: | Line 6: | ||
<br> | <br> | ||
*Squeak6.0 Desktop <blockquote>This is the current level used by the DGUI Project which runs direct on a Mac, Windows, or Linux desktop or remote from a MCP cell.</blockquote><div style="color: yellow;background-color:black;float: right;"> [https://ns2.meansofproduction.biz/SPO/run <span style="color: cyan;">WEBSPO</span>] is set as the home panel for DCMS devops users.</div> | *Squeak6.0 Desktop <blockquote>This is the current level used by the DGUI Project which runs direct on a Mac, Windows, or Linux desktop or remote from a MCP cell.</blockquote><div style="color: yellow;background-color:black;float: right;"> [https://ns2.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. | *The SqueakJS SPO subset (WEBSPO) runs in browsers from images on a browser disk.<blockquote> Desktop is the reference SPO environment, the web version is a convenience for DCMS users. At this writing SqueakJS lacks critical function which it looks like I will have to supply so this is more of an intention than a current capability.</blockquote> | ||
<br>On fileIn, a SPO level presumes a level of squeakmap, monticello, etc. but thereafter generally diverges in its internal squit repo. | <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 | 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> | <br></blockquote></blockquote> | ||
