Skip to content

REDBEAM 0.1.0 — Windows Fluent shell

Choose a tag to compare

@testusercar testusercar released this 04 Sep 16:28
· 10 commits to main since this release

Construction quantity takeoff from PDF drawings, on a Windows 11 Fluent shell.

Which file

You have Download
A normal Windows PC or laptop REDBEAM_0.1.0_x64-setup.exe
A Snapdragon / ARM device REDBEAM_0.1.0_arm64-setup.exe
Group-policy deployment the matching .msi

Both installers are unsigned, so Windows SmartScreen will say "Windows
protected your PC"
on first run. Click More info → Run anyway. They install
per-user to %LOCALAPPDATA%\REDBEAM and need no administrator rights.

The architecture in each filename is real, checked against the PE header rather
than the build label: 0xAA64 for arm64 and 0x8664 for x64.

What is in this build

The shell is Windows, not a theme of one. Mica sits behind chrome that
paints nothing — the app adds no tint of its own, so the desktop keeps its own
colour. The accent is read from your Windows theme (AccentColorLight2, the
step WinUI uses on a dark ground), so REDBEAM matches every other window on your
machine. Segoe UI Variable, Cascadia Mono for figures, Fluent's 4/8 radii.

One sidebar. The 44px icon rail and the 300px panel merged: icons sit in a
strip, the active one expands into a labelled tab, and the drawing got the 44px
back. Collapsed it falls to Fluent's 48px compact navigation.

One command bar. Three floating pills over the drawing became a single
acrylic bar with separators and an overflow, shedding controls as the window
narrows instead of stacking into rows.

A takeoff that refuses to guess. An uncalibrated sheet blocks its quantity
rather than approximating it; a blocked line shows an em dash, never a zero.

Known gaps

  • The scope configurator is half-built — required measures are marked, but the
    measure captions, unit combo boxes and the derived-triple hint are designed
    and not yet implemented.
  • Accuracy against a human estimator's takeoff has not been measured. The oracle
    is in the repository; the comparison run has not been done, so every accuracy
    claim is still self-consistency.
  • No update endpoint is configured. The updater says so rather than claiming
    this copy is current.