MCP-CMS: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
No edit summary
No edit summary
Line 182: Line 182:
  'JCL' means things defined by an M-TRAN phrase grammar which can contain pure MINT blocks but general end use procedures are meant to be in Algol dialects. I dont mean it to be an acronym being both more general than job control and serving as the macro assembler of MCP. MCP thus maintains a distinction between what it and the host machine directly interpret.
  'JCL' means things defined by an M-TRAN phrase grammar which can contain pure MINT blocks but general end use procedures are meant to be in Algol dialects. I dont mean it to be an acronym being both more general than job control and serving as the macro assembler of MCP. MCP thus maintains a distinction between what it and the host machine directly interpret.
<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 st 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", and the pair functioning as  the IDE and GUI of DCP/MCP (DGUI/SPO). Much of it can run headless and minimal or no interaction with it by end or even DevOps users is a supported path. 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", and the pair functioning as  the IDE and GUI of DCP/MCP (DGUI). Much of it can run headless and minimal or no interaction with it by end or even DevOps users is a supported path. 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.
   </div>
   </div>
</blockquote><br><br>
</blockquote><br><br>