CodeBrix.Platform.TerminalView.ApacheLicenseForever 1.0.254.167

CodeBrix.Platform

CodeBrix.Platform is a cross-platform desktop UI framework for .NET. You write your application once against the WinUI XAML API surface (Microsoft.UI.Xaml.* controls, XAML markup, code-behind, and data binding), and CodeBrix.Platform renders it natively on Windows, Linux, and macOS through a Skia-based rendering engine — one shared UI and business-logic codebase, plus one thin executable "head" per platform.

CodeBrix.Platform is provided as a .NET 10 framework and a family of NuGet packages: the core framework package CodeBrix.Platform.ApacheLicenseForever, one CodeBrix.Platform.Runtime.Skia.* package per platform head, and a set of optional add-in packages listed below. Every package in the family is catalogued, with a full description of each one, in CODEBRIX-PLATFORM-README.md.

CodeBrix.Platform supports applications and assemblies that target Microsoft .NET version 10.0 and later. Microsoft .NET version 10.0 is a Long-Term Supported (LTS) version of .NET, and was released on Nov 11, 2025; and will be actively supported by Microsoft until Nov 14, 2028. Please update your C#/.NET code and projects to the latest LTS version of Microsoft .NET.

Installation

An application needs exactly two packages to start: the core framework in its shared class library, and one platform head package in each head executable. For a Linux X11 head:

dotnet add package CodeBrix.Platform.ApacheLicenseForever
dotnet add package CodeBrix.Platform.Runtime.Skia.X11.ApacheLicenseForever

Note that the NuGet package ID and the namespace are different - there is no package named plain CodeBrix.Platform:

• NuGet package ID: CodeBrix.Platform.ApacheLicenseForever
• Assembly and primary namespaces: Microsoft.UI.Xaml.* and Windows.* for your UI code, and CodeBrix.Platform.UI.Hosting for the application bootstrap - i.e. using CodeBrix.Platform.UI.Hosting;

XML documentation (IntelliSense) ships alongside the assemblies.

The head package brings the core framework and the shared Skia runtime (CodeBrix.Platform.Runtime.Skia.ApacheLicenseForever) in transitively, along with build targets that set the head's compilation constants. Reference the core package once, in the shared library, and exactly one head package in each head project.

Everything else is optional. Each add-in package in the table below is added to the shared library alongside the core package, and each one ships its own AGENT-README.txt describing its API in full — read that file for the add-in you are using:

dotnet add package CodeBrix.Platform.AudioPlayer.ApacheLicenseForever

CodeBrix.Platform supports:

• The WinUI XAML API surface — controls, panels, styles, resource dictionaries, templates, visual states, animations and data binding — written exactly as documented for WinUI
• Skia rendering on six platform heads: Windows Win32, Windows WPF, Linux X11, native Linux Wayland, the Linux frame buffer (kiosk and embedded devices with no desktop), and macOS (Apple Silicon and Intel)
• Software and GPU render paths per head (OpenGL on Win32 and X11, Metal on macOS), selected by the host builder or by FeatureConfiguration
• One shared codebase: a .Core class library, a .UI shared project of XAML, and one thin executable head project per target platform
• Application windowing (AppWindow, OverlappedPresenter), UI-thread dispatching (DispatcherQueue) and navigation
• Windows.Storage files and folders, file/folder/save pickers, and the clipboard
• Font loading and preloading, Unicode/ICU text handling, and shaped bidirectional text
• Add-in packages for 2D and 3D drawing, SVG, Lottie animation, media, audio and MIDI, video, an embedded browser, a terminal view, charts, flex layout, host-free text layout, persisted settings, and a full code editor
• A diagnostics overlay, and a logging bridge onto Microsoft.Extensions.Logging

Mobile (iOS/Android) and WebAssembly/browser targets are out of scope for this framework.

How an app is structured

A CodeBrix.Platform solution has three kinds of projects:

1. .Core — a class library holding your application logic, view models, and the framework + add-in NuGet package references.
2. .UI — a shared project (.shproj + .projitems) holding the shared XAML: App.xaml and your views.
3. One executable "head" per platform — a thin project that references .Core, imports the .UI shared project, and references exactly one platform head package.

Packages

The framework and add-in packages are referenced by the .Core library; each head project references exactly one of the Runtime.Skia.* host packages.

The WebView package is referenced once, in the .Core library, like the other add-in packages — every head gets it, it activates on the Linux heads, and it is inert on Windows/WPF/macOS (which have built-in WebView support). On Linux it uses the distro's WPE WebKit engine at run time, which must be installed:

sudo apt install libwpewebkit-2.0-1 libwpebackend-fdo-1.0-1 libwpe-1.0-1

Sample Code

A platform head's startup

using CodeBrix.Platform.UI.Hosting;

var host = CodeBrixPlatformHostBuilder.Create()
    .App(() => new App())
    .UseWindowsWin32()   // or UseWindowsWpf / UseLinuxX11 / UseLinuxWayland / UseLinuxFrameBuffer / UseMacOS
    .Build();

host.Run();

A minimal page

<Page
    x:Class="MyApp.Views.MainPage"
    xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
    xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml">
    <StackPanel HorizontalAlignment="Center" VerticalAlignment="Center">
        <TextBlock Text="Hello from CodeBrix.Platform" />
        <Button Content="Click me" Click="OnClick" />
    </StackPanel>
</Page>

using Microsoft.UI.Xaml.Controls;

namespace MyApp.Views;

public sealed partial class MainPage : Page
{
    public MainPage() => InitializeComponent();
    void OnClick(object sender, Microsoft.UI.Xaml.RoutedEventArgs e) { /* ... */ }
}

Using an add-in package from XAML

<Page
    x:Class="MyApp.Views.PlayerPage"
    xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
    xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
    xmlns:audio="using:CodeBrix.Platform.UI.AudioPlayer.Skia">
    <Grid>
        <audio:AudioPlayer x:Name="Player" Source="ms-appx:///Assets/song.mp3" AutoPlay="True" />
        <Slider VerticalAlignment="Bottom" Margin="16"
            Maximum="{Binding DurationSeconds, ElementName=Player}"
            Value="{Binding PositionSeconds, ElementName=Player, Mode=TwoWay}" />
    </Grid>
</Page>

Documentation

The NuGet package includes AGENT-README.txt, a complete API reference and usage guide written for AI coding agents - point your agent at that file when it is writing code against this library.

Each add-in package ships its own AGENT-README.txt in the root of that package, covering that add-in's API on its own. README-INDEX.txt maps every documentation file in this repository to the package it documents, and CODEBRIX-PLATFORM-README.md is the catalogue of the whole CodeBrix family.

Additional sample code and usage examples are available in the sample applications in this repository — one per add-in, each building for every head: https://github.com/ellisnet/CodeBrix.Platform/tree/main/samples/CodeBrixPlatform

The canonical reference application, JustBetweenUs, ships a complete app across all six platform heads: https://github.com/ellisnet/JustBetweenUs — see the CodeBrixPlatform/ folder.

License

CodeBrix.Platform is licensed under the Apache License 2.0 - see the LICENSE file. Two packages in the family carry a different license, named in their package IDs: CodeBrix.Platform.SkiaSharp.Views.MitLicenseForever is MIT, and CodeBrix.Platform.MediaPlayer.LgplLicenseForever is LGPL-2.1-or-later.

For licensing and provenance information about the open source code included in this package, see THIRD-PARTY-NOTICES.txt.