The Quarterdeck is the rear section of a ship's upper deck, traditionally reserved for the commanding officer.

QDeck

Helm values are structured data, not plain text.

QDeck renders them as navigable tables, not walls of YAML.

• See how your values differ from chart defaults — additions, removals, and overrides at a glance
• Preview rendered templates as you edit values. No more save-run-check cycles.
• Navigate sub-charts and their values in a single view. No need to juggle multiple files.
• Works with local charts on disk
• macOS, Windows, Linux

Development

QDeck is a Gio-based Go GUI for visually exploring Helm chart values, layered on top of the helm.sh/helm/v3 library.

Project follows Conventional Commits naming.

Prerequisites:

• Go 1.25.0
• golangci-lint

# build binary
# on macOS you may need CC=/usr/bin/clang explicitly
go run .

# lint
golangci-lint run --fix

Linux Text Rendering

Gio's GPU text renderer produces grey/fuzzy text on Linux (Mesa OpenGL) due to three framework-level issues: transparent framebuffer compositing, gamma-incorrect alpha blending (gio#70), and a 32-glyph batch boundary that creates visible vertical seams with monospace fonts. These do not reproduce on macOS (Metal) or Windows (Direct3D 11) because their GPU rasterisers handle sub-pixel positioning deterministically.

Workaround applied:

• Custom label/editor renderer (ui/widget/label.go) with a 256-glyph buffer and integer pixel-grid snapping — all text must be rendered through widget.LayoutLabel / widget.LayoutEditor, never via Gio's lbl.Layout(gtx) directly

Vendored Gio (Windows pointer reliability)

third_party/gio/ holds a local fork of gioui.org v0.9.0. go.mod replaces the upstream import with this fork. Two Windows-specific patches sit alongside it in third_party/:

0001 — refresh PointerID on Press and Enter

third_party/0001-gesture-refresh-PointerID-on-Press-and-Enter.patch. Submitted upstream at lists.sr.ht/~eliasnaur/gio-patches/patches/69089.

Why: upstream gesture.Click and gesture.Hover lock their internal pid field to the first PointerID they ever see — both refresh it only when !c.hovered / !h.entered. On Windows, Gio enables EnableMouseInPointer(1) (app/os_windows.go), which causes the OS to assign different PointerIDs to the same physical mouse across focus changes, window leave/re-enter, and similar events. Once the gesture is "stuck" with a stale pid, every subsequent Press whose PointerID doesn't match is silently dropped (the pid != e.PointerID check breaks out before reaching c.pressed = true and the event return). Most visibly this made clicks no-op on multi-line override editors, where widget.Editor's internal clicker (a gesture.Click) ate the press without positioning the caret.

Patch: refresh pid on every Enter / Press so the gesture tracks whichever pointer is currently interacting. 14 lines added, 12 removed. No behavioural change on macOS/Linux.

0002 — stable PointerID for the mouse

third_party/0002-app-windows-stable-PointerID-for-mouse.patch. Submitted upstream at lists.sr.ht/~eliasnaur/gio-patches/patches/69233.

Why: the Windows backend reported two different PointerIDs for the same physical mouse — scrollEvent omitted PointerID from its pointer.Event so it defaulted to 0, while pointerUpdate forwarded whatever ID Windows assigned (typically 1+). Gio's pointerQueue keys state.pointers by PointerID, so a single mouse produced two persistent entries. The phantom (the scroll-derived one) accumulated entered tags it never released — subsequent moves went to the other entry's id, so no Leave events ever cleared it — and ran hit-test every frame at the user's last scroll-wheel position. Because state.cursor is threaded through every pointer in pointerQueue.Frame's loop, the phantom's hit-test overwrote the live pointer's cursor resolution every frame: hovering an anchor badge correctly resolved CursorPointer, then the phantom (sitting over an editor cell) overwrote it with CursorText for the same frame. Same mechanism produced the "two rows hovered at once" symptom — phantom pointer's entered tags never released. EnableMouseInPointer PID drift across focus events compounded the problem with additional phantom entries.

Patch: normalise all Source=Mouse events to a single stable PointerID (^pointer.ID(0)) at the platform layer so pointerQueue always sees one entry per physical mouse. Touch keeps Windows-assigned IDs because multi-touch needs distinct pointers per finger. The chosen sentinel is max-uint so it cannot collide with Windows-assigned touch finger IDs.

Removing the fork

When the upstream patches are merged and released, drop the replace directive in go.mod, bump gioui.org to the release, delete third_party/gio/, both .patch files, the drift-check step in CI, and this section.

License

Copyright © 2026 bosiakov

Licensed under MIT (see LICENSE).

The font ui/platform/font/FiraCode-Medium.ttf is licensed under the OFL-1.1. See ui/platform/font/LICENSE for details.

All fonts are legally licensed to Yauheni Basiakou via MyFonts.