MCP-CMS: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
No edit summary
No edit summary
Line 183: Line 183:
<br><br>
<br><br>
  DCP/MCP is embodied in a central </html>[[:en:Simula|simulacrum]]<html> containing an object model for them. SPO a system supervisor GUI, and LibraryBrowser which maps code trees to MCP object files and maintains MCP file system attributes, run as a Smalltalk vm/image in the regular MCP job mix. LibraryBrowser/SPO are the things an end user
  DCP/MCP is embodied in a central </html>[[:en:Simula|simulacrum]]<html> containing an object model for them. SPO a system supervisor GUI, and LibraryBrowser which maps code trees to MCP object files and maintains MCP file system attributes, run as a Smalltalk vm/image in the regular MCP job mix. LibraryBrowser/SPO are the things an end user
works with to perform dev/ops with the former constituting a "WFL workframe",  the pair functioning as  the IDE and GUI of DCP/MCP (DGUI). Much of it can run headless, the form which the actual DCP can dynamically change by altering its methods, and the one used by non-KEE users. Separately, an available FOSS visual programming pkg is being adapted for what I am calling DS G based on my experience with LabView/G, and which will be developed before WFL but with intent of later being a fa&ccedil;ade for it thru LibraryBrowser.
works with to perform dev/ops with the former constituting a "WFL workframe",  the pair functioning as  the IDE and GUI of DCP/MCP (DGUI). Much of it can run headless, the form which the actual DCP can dynamically change by altering its methods, and the one used by non-KEE users. Separately, an available FOSS visual programming pkg is being adapted for what I am calling DS G based on my experience with LabView/G, and which will be developed before WFL but with intent of later being a fa&ccedil;ade for it in concert with LibraryBrowser.
   </div>
   </div>
</blockquote><br><br>
</blockquote><br><br>