Kazo.Os.AppSdk.VirtualKeyboard
3.0.0
dotnet add package Kazo.Os.AppSdk.VirtualKeyboard --version 3.0.0
NuGet\Install-Package Kazo.Os.AppSdk.VirtualKeyboard -Version 3.0.0
<PackageReference Include="Kazo.Os.AppSdk.VirtualKeyboard" Version="3.0.0" />
<PackageVersion Include="Kazo.Os.AppSdk.VirtualKeyboard" Version="3.0.0" />
<PackageReference Include="Kazo.Os.AppSdk.VirtualKeyboard" />
paket add Kazo.Os.AppSdk.VirtualKeyboard --version 3.0.0
#r "nuget: Kazo.Os.AppSdk.VirtualKeyboard, 3.0.0"
#:package Kazo.Os.AppSdk.VirtualKeyboard@3.0.0
#addin nuget:?package=Kazo.Os.AppSdk.VirtualKeyboard&version=3.0.0
#tool nuget:?package=Kazo.Os.AppSdk.VirtualKeyboard&version=3.0.0
Kazo.Os.AppSdk.VirtualKeyboard
A reusable, host-agnostic on-screen keyboard and a keyboard-aware split container. The keyboard
never fills a focused text field and contains no <input>/contenteditable element anywhere, so
it can never itself trigger a native on-screen keyboard — it only raises typed key events to
whatever target the host wires up.
Wrap the content you want to stay visible above the keyboard in VirtualKeyboardHost. The content
region shrinks via ordinary CSS flex layout when the keyboard docks below it:
@using Kazo.Os.AppSdk.VirtualKeyboard
<VirtualKeyboardHost IsKeyboardVisible="_showKeyboard"
Options="_keyboardOptions"
OnKeyPressed="HandleKeyAsync">
<MyTextSurface />
</VirtualKeyboardHost>
private VirtualKeyboardOptions _keyboardOptions = new() { ShowModifierRow = true };
private Task HandleKeyAsync(VirtualKeyPressedEvent evt)
{
// Decide what the key means for your own target — e.g. append evt.Text to a buffer,
// or translate evt.Key into your own domain's key contract.
return Task.CompletedTask;
}
Kazo.Os.AppSdk.Terminal consumes this package to drive the Terminal's line-mode input and,
through the existing full-screen key-event pipeline, full-screen commands like nano with no
changes to those commands.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- Kazo.Os.AppSdk (>= 3.0.0)
- Microsoft.AspNetCore.Components.Web (>= 10.0.14)
NuGet packages (1)
Showing the top 1 NuGet packages that depend on Kazo.Os.AppSdk.VirtualKeyboard:
| Package | Downloads |
|---|---|
|
Kazo.Os.AppSdk.Terminal
Kazo OS App SDK for terminal commands and the embeddable terminal contract (IKazoTerminal, KazoConsole). |
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 3.0.0 | 49 | 11/5/2026 |
Kazo OS 3.0.0, changes for app developers:
- Backups end in .kosbak, design tokens are --kos-*, diagnostics are KOS*. The last short HOS names become KOS. New backups are .kosbak files; an older .hosbak backup can still be restored. The CSS variables of the design system are now --kos-* (with data-kos-* attributes and kos-* classes): a theme file or theme pack written with --hos-* is still read, and saved themes and settings are updated at the first start. Build diagnostics are now KOSAPP, KOSSDK, KOSWEB, KOSBG and KOSCHG, with the same numbers: update NoWarn and pragma lists.
- Commands, files, app ids and settings take the Kazo OS names. hackpkg becomes kazopkg and hackbackup becomes kazobackup (the old names still work and print a warning), app packages and theme packs use .kazoapp and .kazotheme (the old .hackapp and .hacktheme are still read), the OS files move to /etc/kazoos, ~/.config/kazoos and /etc/kazoweb, the store is called Kazo OS Store, ASP.Hack becomes ASP.Kazo and Hack Paint becomes Kazo Paint. The server and the PWA read the KazoOs configuration section and KAZOOS_ variables, and still read HackerOs and HACKEROS_. The dotnet new templates are now kazoos-window, kazoos-solution... App ids become org.kazoos.*, capabilities kazoos.*, and the browser databases, theme ids and caches take the kazoos and kazoweb names.
- HackerOS is now called Kazo OS. The name HackerOS was already used by a Linux distribution. The OS now shows the name Kazo OS everywhere: window title, installed app, sign-in screen, notifications and documentation.
- SDK 3.0: the Kazo.Os.* packages and the Kazo* types. Every package moves from HackerOs.* to Kazo.Os.* (Kazo.Os.AppSdk, Kazo.Os.Templates...) and every SDK type from Hack* to Kazo* (HackFile becomes KazoFile, HackerIcon becomes KazoIcon, and the HackIcon record becomes KazoSurfaceIcon). The version is 3.0.0: an app built on SDK 2.x is refused and must be rebuilt against the new packages.
- The Kazo OS Store workflow of the kazoos-solution template opens its pull request again. The workflow no longer passes --remote to gh repo fork, which current gh versions refuse, and retries the clone of the fork while GitHub creates it.
- The kazoos-solution template names its app project for the Kazo OS Store. store/store.json of a new app repository has a project field, so the catalog builds the app's project instead of the whole solution, whose tests project has no KazoOsPack target.
Release notes: https://github.com/Kazo-ca/Os/releases/tag/v3.0.0