NuActionGUI (legacy) for Visual Studio Code
Language support for legacy-syntax NuActionGUI models — data (.dtm), security
(.stm) and privacy (.ptm) models with embedded OCL constraints:
- Diagnostics from the real compilers and the OCL type checker, as you type: every
syntax error in one pass, semantic and type errors positioned at the construct, privacy
warnings. Editing a
.dtm re-checks the open .stm/.ptm of the same project.
- Syntax highlighting for the three model languages and the embedded OCL.
- Commands: New Project, Generate / Regenerate Web App, Run Generated Web App, Open in
Browser, Restart Language Server.
The extension contains no model logic. It runs the language server and the nag-legacy
command line that ship in the nuactiongui-legacy
Python distribution, out of the environment of the workspace you have open.
This extension is for models written against the original NuActionGUI syntax. For the
successor toolchain use the NuActionGUI extension (infsec.nuactiongui). Both
claim .dtm/.stm/.ptm; enable one or the other per workspace, not both.
Upgrading from 0.1.x
This is the same marketplace listing (infsec.vscode-nag) with a new display name. Two
things changed underneath:
- The language server no longer runs from a source checkout. It ships in the
nuactiongui-legacy Python package: pip install "nuactiongui-legacy[apps]" into the
interpreter the Python extension has selected (or a .venv beside your models). On first
activation without it you get a single error with Install nuactiongui-legacy / Select
Interpreter; nothing else is needed.
- Settings and commands moved to the
nuactiongui-legacy.* namespace. The 0.1.x keys
nag.server.pythonPath and nag.server.command, and the command nag.restartServer, are
still honoured as deprecated aliases, so an existing setup keeps working; the settings UI
shows the replacement.
Requirements
- The Python extension
(installed automatically).
pip install "nuactiongui-legacy[apps]" in the interpreter the Python extension has
selected, or in a .venv beside your models. If it is missing, the extension says so and
offers to install it or to pick another interpreter.
Interpreter resolution order: nuactiongui-legacy.pythonPath → the Python extension's
selected environment → .venv/venv/.env beside the models → VIRTUAL_ENV → python3.
Settings
| Setting |
Default |
Meaning |
nuactiongui-legacy.pythonPath |
"" |
Interpreter override for the server and the CLI |
nuactiongui-legacy.serverCommand |
"" |
Escape hatch: exact command (string or argv array) that starts the language server |
nuactiongui-legacy.outputFolder |
output |
Where generated apps go, relative to the workspace (nag-legacy -o) |
nuactiongui-legacy.port |
5002 |
Port for the generated Flask app |
Workflow
- NuActionGUI (legacy): New Project →
models/<name>/project.{dtm,stm,ptm}.
- Edit the models; diagnostics appear as you type.
- Generate Web App runs
nag-legacy -p <project> -o output in a terminal.
- Run Generated Web App runs
nag-legacy --run <project>; Open in Browser opens it.
Generated apps need Python < 3.14 (their Flask stack); the CLI says so otherwise.
A model file under models/<name>/ is addressed by name; a model file anywhere else
by its folder.
Development
npm install
npm test # typecheck, esbuild bundle, client tests in plain Node
npx vsce package # -> nuactiongui-legacy-<version>.vsix
Press F5 in VSCode to run the extension from source. The client tests
(test/extension.test.js) run against the built bundle with stub environments; the
server's own tests live in the Python repository (tests/langserver).
Publishing
See RELEASING.md in this folder: marketplace identity, ephemeral PAT
policy, the gate (npm test, npx vsce package, a real install over the previous version)
and the publish/verify steps. PyPI first, then the extension.
License
MIT.