WFL/DCP SPO: Difference between revisions
From Cibernética Americana
Jump to navigationJump to search
| (12 intermediate revisions by the same user not shown) | |||
| Line 5: | Line 5: | ||
<blockquote style="color:black;background-color:white;"><blockquote> | <blockquote style="color:black;background-color:white;"><blockquote> | ||
<br> | <br> | ||
* Full Function <blockquote>Squeak 6 is the version used as the direct control cell of | * Full Function <blockquote>Squeak 6 is the version used as the direct control cell of DCP/MCP and this is the reference and only complete DGUI. The code can run on Mac and Windows but I only support those platforms via remote desktop to a linux vm/image. FileOut sources to port to other st setups.</blockquote> | ||
* Limited Function | * Limited Function | ||
**A SqueakJS SPO (WEBSPO) runs from browsers ...<blockquote> .. as a convenience for DevOps 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 effort subject to these limitations.</blockquote><br><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> | |||
**A SqueakJS SPO (WEBSPO) runs from browsers ...<blockquote> .. as a convenience for | **Pharo <blockquote>As in the squeakjs case (vm reasons) and for additional ones specific to it, Pharo support by me is limited to a first pass on fileIn of the above sources. In principle, the Pharo version should be intermediate between the Squeak and squeakjs ones but I dont intend to personally make it so.</blockquote> | ||
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 | WEBSPO actually just has limited ODT functionality and cannot control a DCP.<br><br> | ||
</blockquote></blockquote> | </blockquote></blockquote> | ||
=== vs. DS G === | |||
Altho they have obvious superficial similarities, the visual programming paradigm and smalltalk are distinct, historically and in this novel. DS G is developed from the start based on node red building bottom up with DCP/MCP custom nodes and other contrib flows like the excellent Xstate smxstate. Smalltalk is about a decade older that G (LabView) FWIW. A G lang implies a façade over some generated backend and that's kinda the opposite of st which generates bytecodes for a vm tightly bound to the lang. It is also less of a general purposes lang with its control system and instrumentation focus. | |||
<hr> | |||
<small>Rest of this page unmaintained background on the SPO concept, in a running image the current code should be consulted in a Browser under the DomainSpace category .</small> | <small>Rest of this page unmaintained background on the SPO concept, in a running image the current code should be consulted in a Browser under the DomainSpace category .</small> | ||
