Desktop Package

heliokit-desktop is the protected desktop distribution. It is separate from the original SWAS/SWVIZ desktop packaging path and does not replace or modify that existing delivery flow.

Runtime model

The desktop wheel expects a controlled Windows environment:

Requirement	Reason
64-bit CPython 3.10	Native modules and compiled extensions target CPython 3.10.
Locked scientific dependencies	Heavy libraries such as VTK, Qt, TensorFlow, and Torch are provided by the environment instead of being copied into the wheel.
Matching build/runtime template	Native packages are not ABI-independent across arbitrary Python distributions.

Environment setup

Use one of the two supported Python 3.10 setup paths described in Get Started: an existing controlled 64-bit CPython 3.10 environment, or a dedicated Conda environment. The Conda path is recommended for desktop users. Install the runtime dependency set provided for your release before installing the desktop package:

conda create --name heliokit python=3.10 --yes
conda activate heliokit
python -m pip install --upgrade pip

Install and run

python -m pip install heliokit-desktop
pythonw -m heliokit_desktop

The desktop wheel deliberately does not bundle heavy runtime libraries such as VTK, Qt, TensorFlow, and Torch. Those dependencies must already be present in the controlled environment.

Inspect the component host from the same environment:

python -m heliokit_desktop.cli components list

Protection model

The production desktop distribution compiles desktop business modules to CPython 3.10 native extensions and compiles bundled host/component sources to bytecode before removing source files from the wheel payload. This raises the cost of casual reverse engineering, but it is not a cryptographic protection boundary.

Uninstall

python -m pip uninstall heliokit-desktop