LabSpace.Workbench 0.3.0-alpha.1

<div align="center">

LabSpace

A graphical instrumentation studio for desktop and the browser.

Build front panels, connect typed block diagrams, inspect live values and run simulated signal-processing programs in a shared Uno Platform application.

Open the studio · User guide · Typed structures · Architecture · Compatibility

</div>

0.3 — Structured programs and cross-VI debugging

0.3.0-alpha.1 adds executable numeric/string/Boolean/error Case Structures, ordered sequence frames and typed sequence locals, a compiled scalar Formula Node, error-cluster and complex-number controls and functions. Staged editors validate changes before Apply, named terminals support right-click creation and branching, and nested debugging includes step-out. Structure frame selectors, actual-body previews and resize handles are shared by the desktop and browser editors.

Open Case Dispatch.vi: the command run selects a frame producing 42. Open Sequence Pipeline.vi: an earlier frame writes 21, a later formula computes 84. Errors and Complex.vi displays a real typed error cluster and computes the magnitude of 3 + 4i as 5. Edit their case labels, formula, error code/source or real/imaginary components to change actual results. These are executable diagrams, not animations.

Formula Control Flow.vi evaluates a bounded for loop with continue into separately wired results 84 and 9. Open View → Debug window to inspect its probe, switch to another VI and use Locate to return. Debugging flags and probe/breakpoint overrides are session state: toggling them does not dirty source or create Undo records.

Debugger guide · Advanced structures guide · Typed loops and registers · Compatibility ledger

LabSpace is a working independent implementation inspired by the classic NI LabVIEW workflow. It is not yet a complete, pixel-identical or binary-compatible LabVIEW replacement. NI VIs, the entire G language, instrument drivers and real-time/FPGA targets are not implemented. The compatibility ledger records exact supported behavior and remaining boundaries. No NI source code, proprietary artwork, drivers or runtime are included.

Explore the application

Eight executable examples are included: Signal Analysis.vi, Arithmetic.vi, Stateful Loop.vi, Indexed Accumulator.vi, Case Dispatch.vi, Sequence Pipeline.vi, Errors and Complex.vi, and Formula Control Flow.vi. The plots and indicators display results from their real dataflow graphs, not decorative sample animation. Acquisition is explicitly simulated.

Press Ctrl+Space, search for a function/control, press Enter, then click to place it. Escape cancels without editing. Right-click a canvas for the corresponding context palette. Ctrl+E switches editors; Ctrl+R runs; F6 runs continuously; F10/F11 step over/into; Ctrl+F11 steps out. Canvas undo and clipboard commands do not replace text-field editing behavior.

Rendering and performance

Both editors render with SkiaSharp through Uno's SKCanvasElement. The browser is a real C#/Uno WebAssembly application, not an HTML imitation of the interface. Browser and native desktop hosts share the model, engines, rendering code and workbench.

Rendering uses retained drawing resources, visible-area culling, cached wire paths, cached SKPicture structure previews and extrema-preserving waveform decimation. Immutable connector contracts are resolved through a weak identity cache. Graphs compile only when needed; pointer geometry edits do not repeatedly compile the dataflow graph.

The workbench targets a 40 ms execution timer and yields nested work after 4,096 transitions or roughly 8 ms checked after the first 16 transitions. Individual kernels still run to completion. Hardware acceleration/fallback depends on the Uno host. DSP/dataflow run in managed C#, not WebGPU compute, and these scheduling limits are not hard-real-time guarantees.

Run tools/LabSpace.Benchmarks for reproducible engine/FFT timing and allocation measurements. These are managed-engine measurements, not GPU or UI frame times. See architecture and performance.

Download

Every release ships a self-contained, single-file desktop app — no .NET install needed:

Extract and run LabSpace (LabSpace.exe on Windows). Builds are not code-signed yet: on macOS clear the quarantine flag with xattr -d com.apple.quarantine LabSpace; on Windows choose More info → Run anyway in SmartScreen. Verify downloads against SHA256SUMS. Releases also include the browser distribution and engine benchmarks.

The libraries below are published to NuGet.org, e.g. dotnet add package LabSpace.Core.

Reusable libraries

All nine libraries are published to NuGet.org with symbols. The host application and tests are not library packages.

Use the engine independently

using LabSpace.Dataflow;
using LabSpace.Documents;

var vi = StructuredExamples.IndexedAccumulator();
var loop = vi.Diagram.Nodes.Single(node => node.Kind == "for");
var graph = GraphCompiler.Compile(vi.Diagram);
var runtime = new DataflowRuntime();

using var cancellation = new CancellationTokenSource();
var frame = runtime.Run(graph, cancellation.Token, maximumNodes: 100_000);
Console.WriteLine(frame.GetOutput(loop.Id, "state").Number); // 15
Console.WriteLine(string.Join(", ", frame.GetOutput(loop.Id, "totals").Samples));
// 1, 3, 6, 10, 15

InstrumentWorkbench(session, storage, fonts) embeds the entire studio in another Uno application. Individual controls and engines are separately reusable. See typed structures for contract definitions and resumable execution.

Build and run

Pinned toolchain: .NET SDK 10.0.401, Uno SDK 6.7.30 / WinUI 6.7.135, and SkiaSharp 3.119.4 with matching managed/native assets. The selected Skia release is Uno-compatible; do not independently upgrade only its managed assembly.

git clone https://github.com/wieslawsoltes/LabSpace.git
cd LabSpace
dotnet workload install wasm-tools --skip-manifest-update
python3 scripts/fetch-assets.py
dotnet test tests/LabSpace.Tests -c Release

The asset script retrieves content-pinned OFL assets and checks their hashes. No proprietary platform fonts are required.

# Windows, Linux or macOS native desktop host
dotnet run --project src/LabSpace.App -f net10.0-desktop \
  -p:LabSpaceDesktopOnly=true

# Browser distribution with the GitHub Pages project base path
dotnet publish src/LabSpace.App -f net10.0-browserwasm -c Release \
  -o artifacts/publish -p:WasmShellWebAppBasePath=/LabSpace/
python3 scripts/check-native-abi.py
python3 scripts/collect-site.py artifacts/publish artifacts/site
python3 scripts/serve-site.py --directory artifacts/site --port 4173

Open http://localhost:4173/LabSpace/. In another terminal, run the real-pointer acceptance suite:

npm install --ignore-scripts
npx playwright install chromium
npm run test:browser

See development for dependencies, packaging, base paths, opt-in test diagnostics and deployment provenance.

Quality and releases

GitHub Actions runs engine tests, three-OS desktop builds, a real Uno browser publish, keyboard/pointer acceptance, screenshot capture, and Pages deployment with a source-commit check. The same browser workflows run against the public deployment. Browser tests inspect read-only diagnostics but edit the application using real input; they do not call private model-mutating test functions.

The release workflow runs for v* tags, matching main-branch changes or a supplied manual version. It runs storage and engine tests, publishes self-contained single-file desktop executables for Windows, macOS and Linux (x64 and arm64), packs all nine versioned libraries with symbols, audits resolved Skia versions, publishes a browser distribution, records engine benchmarks and emits SHA256SUMS. Tags attach all assets to a GitHub Release (prerelease for - versions) and publish the packages to NuGet.org with Trusted Publishing (OIDC, no stored API key) from the protected nuget environment. Other runs are dry runs: they build and upload every asset as workflow artifacts but publish nothing. Code-signed desktop installers and physical hardware/GPU certification are not included.

Files, safety and licensing

Save projects as .labspace.json. Version-1 and version-2 files migrate to version 3. Earlier LabSpace releases cannot read version-3 files; retain original copies when migrating. NI .vi, .ctl and .lvproj files are not imported. Local recovery is not a substitute for explicit saved copies. Imported JSON does not evaluate script or install drivers.

The application is intended for experimentation, education and component development. It is not validated for safety-critical equipment or physical/hard-real-time control.

MIT license · Third-party notices · Contributing · Security · Changelog