Skip to main content

NativeHTMLKit Demo

One window with every NativeHTMLKit example. Pick an example, read its Python, PowerShell, HTML and CSS source, and press Run Python or Run PowerShell to start it as its own native desktop app. No browser, no web server.

The NativeHTMLKit Demo window on KDE Plasma (Wayland), with the Counter example started from it

NativeHTMLKit renders HTML and CSS in a native window and drives it from Python or PowerShell. See the documentation.

Install and start

Python (3.10 or later):

python -m pip install nativehtmlkit-demo
nativehtmlkit-demo

PowerShell (7.x, or Windows PowerShell 5.1):

Install-Module NativeHTMLKit.Demo -Scope CurrentUser
Start-NativeHTMLKitDemo

Each package contains the launcher and all the examples. The Python package installs the nativehtmlkit SDK and nativehtmlkit_ui; the PowerShell module installs the NativeHTMLKit and NativeHTMLKit.UI modules. To run the examples of the other language as well, install that language's package too. The launcher finds Python and PowerShell on PATH and tells you what is missing.

Supported platforms are those of the SDKs: Linux (KDE Plasma on Wayland is the primary desktop) and Windows 10/11 or Server 2022, x64.

What is in the window

  • Examples on the left: the SDK examples (direct HTML/CSS plus events) and the NativeHTMLKit UI examples (reactive components). Type in the filter box to narrow the list.
  • Source tabs: the files of the example exactly as they ship. The HTML and CSS tabs show the page. For SDK examples that is the page embedded in the code or loaded from index.html. For UI examples it is the markup NativeHTMLKit UI generates for the first render.
  • Run Python / Run PowerShell start the example in a new process. Examples run from a working folder under your temporary directory (nativehtmlkit-demo/). The log viewer gets a sample log file that grows while it runs.
  • Running examples at the bottom: Stop, or open the Output tab to see what an example printed and why it exited.

The examples come from the Python SDK, PowerShell SDK and NativeHTMLKit UI repositories. Their guides explain each one.

Self-test

nativehtmlkit-demo --self-test and Start-NativeHTMLKitDemo -SelfTest run the launcher headless, check every example and its source tabs, start a few examples in each installed language and stop them again. They print PASS/FAIL/SKIP lines and exit with code 0 when nothing failed.

Development

python scripts/sync_examples.py      # copy the examples from sibling SDK/UI checkouts, write content/catalog.json
python -m pytest tests               # content checks
PYTHONPATH=python/src python -m nativehtmlkit_demo          # run from the checkout
pwsh -File powershell/NativeHTMLKit.Demo/Demo.ps1            # (needs the NativeHTMLKit modules)
python scripts/build.py              # dist/: wheel, module zip, SHA256SUMS

content/examples/ is generated; change an example in its own repository, then sync again.

License

MIT. The examples keep the licenses of their repositories (copies in content/examples/LICENSES/).

Metadata

Release files for nativehtmlkit-demo 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for nativehtmlkit-demo 0.1.0
File Interpreter ABI Platform Actions
nativehtmlkit_demo-0.1.0-py3-none-any.whl Python 3 none any Details for nativehtmlkit_demo-0.1.0-py3-none-any.whl

Release files / nativehtmlkit_demo-0.1.0-py3-none-any.whl

Download URL nativehtmlkit_demo-0.1.0-py3-none-any.whl
Size 238.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
ccd37f2d74f346cf0b9f880b01dfaeb6be3eb2defa4fe3f6acc71cf5a5d4771b
BLAKE2b-256 checksum
How to use checksums
c94965480faf221f7763bee70e988b46be5445109c768b3975b4e81d48d4c168
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 16, 2026.

Transparency log

Security for nativehtmlkit-demo 0.1.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

1 file in this release has been uploaded with provenance metadata.

Attestation for nativehtmlkit_demo-0.1.0-py3-none-any.whl

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 16, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page