WFL/DCP SPO: Difference between revisions
From Cibernética Americana
Jump to navigationJump to search
No edit summary |
No edit summary |
||
Line 3: | Line 3: | ||
A link to download the Squeak plug-in so you can run a SPO¹ will be a the foot of this page soon. | A link to download the Squeak plug-in so you can run a SPO¹ will be a the foot of this page soon. | ||
== | == SPO == | ||
In MCP based systems one or more consoles can function as the "SPO", the system operator interface. In our system, this | In MCP based systems one or more consoles can function as the "SPO", the system operator interface. Originally it stood for "Supervisory Print Out" in the early MCP but has become "Single Point Operations" service in current MCP. In our systems it corresponds to our merge and extend operation on the FileList and SqueakMap tools in an object called "SmalltalkPackagedOperations". | ||
In our system, this is the uniform GUI for dominion operations management. | |||
== External Links == | == External Links == | ||
[http://meansofproduction.biz/pub/npsqueak Download SPO plugin] | [http://meansofproduction.biz/pub/npsqueak Download SPO plugin] |
Revision as of 16:34, 13 May 2010
Dominion Lede
A link to download the Squeak plug-in so you can run a SPO¹ will be a the foot of this page soon.
SPO
In MCP based systems one or more consoles can function as the "SPO", the system operator interface. Originally it stood for "Supervisory Print Out" in the early MCP but has become "Single Point Operations" service in current MCP. In our systems it corresponds to our merge and extend operation on the FileList and SqueakMap tools in an object called "SmalltalkPackagedOperations".
In our system, this is the uniform GUI for dominion operations management.