git404hub

what is navius-wpf fr?

lzitser23/navius-wpf — explained in plain English

Analysis updated 2026-05-18

0C#Audience · developerComplexity · 3/5LicenseSetup · moderate

tl;dr

A native WPF port of a web component library, giving Windows desktop apps the same styled, accessible controls without a WebView.

vibe map

mindmap
  root((navius-wpf))
    What it does
      Native WPF components
      No WebView
      Real accessibility peers
    Tech stack
      .NET
      WPF
      C#
      LiveCharts2
    Use cases
      Themed UI components
      Vendor single components
      Match web design system
    Packages
      Primitives
      Ui styled layer
      Motion engine
      Charts wrapper

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

what do people make with this?

VIBE 1

Add a themed, accessible set of UI controls like dialogs, dropdowns, and data grids to a native WPF desktop app.

VIBE 2

Copy a single component's source code into your own project instead of taking a full package dependency.

VIBE 3

Build a WPF app that matches an existing web design system's look and keyboard behavior.

what's the stack?

.NETWPFC#LiveCharts2

how it stacks up fr

lzitser23/navius-wpfanulman/docx-saxatrblizzard/vtmb-sbox-mounter
Stars000
LanguageC#C#C#
Setup difficultymoderatemoderatemoderate
Complexity3/54/53/5
Audiencedeveloperdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

how do i run it?

Difficulty · moderate time til it works · 30min

Requires a .NET 8 or .NET 10 WPF project, components install via NuGet or a source-vendoring CLI tool.

Free to use, modify, and distribute for any purpose, including commercial use, as long as the copyright notice is kept.

in plain english

navius-wpf brings a library of pre-built user interface components, originally designed for websites, over to native Windows desktop applications built with WPF. Instead of embedding a web browser control to reuse the original web version, this project rebuilds each component using WPF's own native tools, so there is no web browser involved anywhere in the stack. Each control is built without a fixed visual appearance baked in, meaning its look can be fully restyled through WPF's templating system while its behavior stays the same. A major focus of the project is accessibility. Each control is connected to a real automation object so that screen readers and other assistive technology on Windows can understand what the control is and how to interact with it, and keyboard navigation is implemented and tested for every component using real application windows rather than simulated ones. The library includes fifty eight basic building block components, covering common elements like buttons, checkboxes, dropdown menus, data tables, tree views, date pickers, and overlay style components such as dialogs, alerts, side panels, menus, toast messages, and tooltips. On top of these, a second package provides twenty ready to use styled components such as a sidebar, a command palette, and a card layout, sharing a consistent visual theme with the original web version. A separate small animation engine provides spring based motion effects that respect the Windows system setting for reduced motion. There is also a lightweight charting package and a command line tool that can copy any single component's source code, along with everything it depends on, directly into your own project so you can customize it freely. The project includes over thirteen hundred automated tests across its different pieces, and documentation for every component, including its exact behavior and any differences from the original web version, is published on a dedicated documentation website. It can be installed as ready-made packages from NuGet, referenced directly from source, or copied component by component using its own command line tool. The project is released under the MIT license.

prompts (copy fr)

prompt 1
Install Navius.Wpf.Primitives and Navius.Wpf.Ui via NuGet and apply the Light theme at app startup.
prompt 2
Use the navius-wpf CLI to vendor the Select component and its dependencies into my project under my own namespace.
prompt 3
Add a NaviusDialog with a confirm and close button to my WPF window using the overlay layer.
prompt 4
Compare navius-wpf's keyboard behavior for a given control against its web catalog counterpart in docs/parity.

Frequently asked questions

what is navius-wpf fr?

A native WPF port of a web component library, giving Windows desktop apps the same styled, accessible controls without a WebView.

What language is navius-wpf written in?

Mainly C#. The stack also includes .NET, WPF, C#.

What license does navius-wpf use?

Free to use, modify, and distribute for any purpose, including commercial use, as long as the copyright notice is kept.

How hard is navius-wpf to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is navius-wpf for?

Mainly developer.

peek the repo → explain another one

This repo across BitVibe Labs

double-check against the repo, no cap.