GPU-first UI substrate
ProGPU
A lightweight GPU foundation for the next generation of .NET interfaces.
View project ↗Wiesław Šoltés Independent open-source engineer
GPU renderers, portable UI frameworks, and the controls that turn them into real tools.
Interactive ecosystem map
Hover or focus a project to reveal its closest collaborators. Each layer is independently useful; the connections are where the larger system appears.
Pixels, vectors, text
Hosts and runtime seams
Controls and diagnostics
Complete working tools
What connects the work
I build the infrastructure behind ambitious .NET desktop software: from pixels and text, through layout and controls, to complete editing environments.
Each project is independent. Together, they form an experiment in what an open, portable desktop stack can become.
Current focus
Five projects pushing the portable .NET desktop forward.
GPU-first UI substrate
A lightweight GPU foundation for the next generation of .NET interfaces.
View project ↗WPF, beyond Windows
Keep the WPF programming model. Change the platform beneath it.
View project ↗Portable WinForms APIs
Classic desktop APIs, carried onto a modern GPU stack.
View project ↗Rendering backend
Avalonia rendering, rebuilt around a direct GPU composition path.
View project ↗Document engineering platform
Build complete document workflows from one composable, cross-platform stack.
View project ↗Selected systems · 01—31
Frameworks, graphics, controls, and tools maintained as parts of a larger open-source ecosystem.
No projects match that search.
Extended archive
Not every maintained repository needs a full feature page. This compact archive preserves discoverability and makes current commitment explicit.
Focused libraries and controls that remain useful parts of the wider portfolio.
A Roslyn source generator, analyzer, and code-fix package for reactive properties, computed observable properties, and change notification.
Roslyn · Reactive · Source generation↗StaticViewLocatorA compile-time Avalonia view locator with convention mapping, generic, base-class, and interface fallbacks, and configurable MSBuild rules.
Avalonia · AOT · Source generation↗XamlToCSharpGeneratorAn Avalonia XAML compiler stack with typed bindings, runtime loading, hot reload and design, language services, editor controls, LSP, MCP, preview, and VS Code tooling.
XAML · Roslyn · Tooling↗PrintingToolsA .NET printing toolkit with discovery, dialogs, preview, pagination, layout, PDF/vector rendering, job submission, and Windows, macOS, and Linux adapters.
Avalonia · Printing · Controls↗NativeMessageBoxA managed and native ABI for advanced message dialogs across Windows, macOS, Linux, iOS, Android, and WebAssembly.
Desktop · Native · Interop↗LottieLottie playback plus reusable frame-loop, composition-backed Skia, and animated shader controls for Avalonia.
Animation · Skia · Avalonia↗MediaPlayerGPU-composited media playback for Avalonia with native platform backends, FFmpeg and LibVLC fallbacks, track/device APIs, and reusable editing workflows.
Media · Avalonia · Controls↗HexViewAn Avalonia hexadecimal viewer and editor with memory-mapped large files, piece-table edits, search and replace, diff, navigation, bookmarks, and patch export.
Binary · Editor · Avalonia↗ThemeManager.AvaloniaA small runtime theme abstraction that initializes Avalonia Fluent or Simple themes and switches the application between light and dark variants.
Themes · Avalonia · Styling↗SvgToXamlA desktop and build-time converter that turns SVG artwork into Avalonia XAML drawings, geometries, and resource dictionaries.
SVG · XAML · Conversion↗RibbonControlAn Avalonia ribbon toolkit with XAML and MVVM composition, tabs, groups, galleries, backstage, key tips, adaptive layout, merging, customization, and JSON persistence.
Controls · Desktop · Commands↗Projects that mark an important chapter, without implying the same current focus.
Working principles
Understand the path from input to pixels, then make each layer observable and replaceable.
Move established programming models forward without discarding the knowledge encoded in existing applications.
Build in public, document the seams, and leave behind reusable foundations instead of isolated demos.