WFL/DCP SPO: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
Line 5: Line 5:
<blockquote style="color:black;background-color:white;"><blockquote>
<blockquote style="color:black;background-color:white;"><blockquote>
<br>
<br>
* Full Function Desktop <blockquote>Squeak 6 is the current level used by the DGUI Project which runs direct on a Mac, Windows, or Linux desktop or via vnc from a MCP cell.</blockquote>
* Full Function Desktop <blockquote>Squeak 6 is the current level used by the DGUI Project which runs direct on a Mac, Windows, or Linux desktop or via vnc from a MCP cell and this is the reference and essentially only full DGUI.</blockquote>
* Limited Function Subsets
* Limited Function Subsets
**Pharo <blockquote>Pharo support is limited for a variety of reasons, with its vm, as in the squeakjs case, being the main limiting factor.</blockquote>
**Pharo <blockquote>Pharo support is limited for a variety of reasons, with its vm, as in the squeakjs case, being the main limiting factor.</blockquote>
**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. Originally I thought SqueakJS lacked working networking/socket functionality but it appears that at least no longer is the case, still evaluating but at this writing assume problems will be cleared subject to what can work in a browser. Browser has some inherent limitations vs a regular VM which together mean desktop will remain the default for DGUI/SPO.</blockquote><div style="color: yellow;background-color:black;float: right;position:relative;top:-20px;"> &nbsp; [https://ns2.meansofproduction.biz/SPO/run <span style="color: cyan;">WEBSPO</span>] is selectable as a home panel view  on devops1.sameboat.</div><br>
**A SqueakJS SPO (WEBSPO) runs from browsers ...<blockquote> .. as a convenience for DCMS 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 best effort under this restriction.</blockquote><div style="color: yellow;background-color:black;float: right;position:relative;top:-20px;"> &nbsp; [https://ns2.meansofproduction.biz/SPO/run <span style="color: cyan;">WEBSPO</span>] is selectable as a home panel view  on devops1.sameboat.</div><br>
On fileIn, a SPO level presumes a level of squeakmap, monticello, etc. but thereafter generally diverges in its internal Squot (git) repo.
On fileIn, a SPO level presumes a level of squeakmap, monticello, etc. but thereafter generally diverges in its internal Squot (git) repo.
Whether in a browser or on a desktop a SPO must be served from a node or cell of a MCP which is DCP managed.<br><br>
Whether in a browser or on a desktop a SPO must be served from a node or cell of a MCP which is DCP managed.<br><br>