WFL/DCP SPO: Difference between revisions
From Cibernética Americana
Jump to navigationJump to search
No edit summary |
|||
| Line 8: | Line 8: | ||
* Limited Function | * Limited Function | ||
**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> | ||
**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 | **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 good enough under subject to these limitations.</blockquote><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><br> | ||
On fileIn, a SPO level presumes a level of squeakmap, monticello, etc. but thereafter generally diverges in its internal git repo.<br> | 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 ODT functionality, it cannot control a MCP.<br><br> | WEBSPO actually just has ODT functionality, it cannot control a MCP.<br><br> | ||
