WFL/DCP SPO: Difference between revisions
From Cibernética Americana
Jump to navigationJump to search
| Line 8: | Line 8: | ||
*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 so this is more of an intention than a current capability until I or someone else address the shortcomings, it does mostly work within the image but network and other issues kill production use.</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. At this writing SqueakJS lacks critical function so this is more of an intention than a current capability until I or someone else address the shortcomings, it does mostly work within the image but network and other issues kill production use.</blockquote> | ||
On fileIn, a SPO level presumes a level of squeakmap, monticello, etc. but thereafter generally diverges in its internal squit repo. | 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 or cell of a MCP which is DCP managed.<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> | ||
</blockquote></blockquote> | </blockquote></blockquote> | ||
