Methodox Wiki
Product documentation
Methodox Home

Editions

Methodox Office comes in two editions, which differ only in what a document's code is allowed to use once you trust it. Everything else, the applications, the formats and the programming model, is the same.

Methodox Office (Standard) Methodox Office + Divooka Compute (Compute)
Installer and folder MethodoxOffice_v<version>_... MethodoxOffice_Compute_v<version>_...
Lua and C# in a document Against the Office object models The same
Divooka graphs in a document The audited Office nodes and the Divooka standard library's pure routines Also every Divooka package whose NRI bindings (*.NRI.dll) are in the Methodox Office folder, in full trust
Python in a document Under a guard: no .NET bridge, no open, exec or eval, and only computing modules can be imported (math, statistics, decimal, re, json, datetime, collections, itertools and similar) Full Python, with the .NET bridge and the packages of your Python environment
Network and files Only through the host's calls, granted per document and remembered in the trust store The same for Lua, C# and Office nodes; packages used in full trust reach what they reach
Immediate mode in the Scripts pane Full access Full access

In both editions, opening a document never runs its code: a document's code runs only after you Enable it, and that choice is remembered against a hash of the code (see Trust). The edition decides what trusted code may then do. Immediate mode is what you type yourself, so it has full access in both.

A graph that uses a node its edition does not allow is refused before anything runs, and the message names the graph and the node; in the graph editor such a node is marked, with the reason on hover. Extensions run under the same rules as a document's code.

Divooka Compute is found, not bundled

Neither edition includes Divooka Compute, the full Divooka editor. Open in Divooka Compute, on the graph editor's strip, opens a document's graph in the Compute installed on the computer, and looks for it in this order:

  1. the program the METHODOX_DIVOOKA_COMPUTE environment variable names;
  2. DivookaCompute.exe beside Methodox Office's own executables;
  3. DivookaCompute.exe in a Divooka Compute folder beside them, or beside the folder they are in;
  4. the Divooka graph editor registered on the computer, when that is Divooka Compute.

When none is found, the button is disabled and its tooltip says that Divooka Compute is not installed. Save in Compute and the graph comes back into the document as one undoable change; if the document's copy changed meanwhile, Methodox Office asks which to keep. For Compute's palette to offer the Office nodes, its plugins folder needs the Divooka.Office.Automation.Nodes.Compute plugin.

See also