Skip to content

Releases: testusercar/redbeam

REDBEAM 0.3.1

Choose a tag to compare

@testusercar testusercar released this 25 Sep 15:48

Hand install of 0.3.1. Copies that shipped as 0.3.0 were built with an empty updater endpoint and will not see the update channel.

REDBEAM 0.3.0 — the parts list as ordered, the dock, Windows' materials

Choose a tag to compare

@testusercar testusercar released this 18 Sep 19:28

Install

Windows. Both installers are unsigned, so SmartScreen will ask once.

  • ARM64 — REDBEAM_0.3.0_arm64-setup.exe or the .msi
  • x64 — REDBEAM_0.3.0_x64-setup.exe or the .msi

The control surface, the surfaces Aaron approved from boards, Windows'
materials, and the parts list as an estimator orders it. Everything visible
in this release was drawn first and built to the drawing; the boards are in
docs/design/.

The parts list, and what each product orders

  • A part is a thing you buy. One line per part with its size as a chip;
    the full/cut breakdown, ordered length and offcut are a detail line
    beneath it, never parts of their own. A run product's installed length is
    an Installed tile, not an order line. Rails, connectors, end caps, joiners
    and trim are an Accessories group. A custom assembly has no Parts section.
    Confidence is one chip on the header, not a note on every line.
  • The tiles show only what the scope measures. No tile reads "—".
  • What each product orders, in Aaron's words: panels — panels and trim;
    planks — planks, carrier rails and trim; baffles — baffles, suspension
    rails, connectors, joiners, end caps; cassettes — cassettes, baffles, end
    caps. Panels never had trim; baffles could never report a rail; planks
    listed connectors and joiners nobody buys. All three corrected.
  • Trim is cut per edge. Every edge of every area — cutouts included —
    rounds up to whole sticks on its own. The whole-perimeter division is gone.
  • A rail is a laid run. Perpendicular to the baffle at each connector
    line, cut from rail stock with its own offcut. The area-over-pitch-over-
    length estimate is gone; without a rail length there are no rails.
  • A plank's connector spacing is its Conn. Max, else its rail spacing,
    else its stock length — several rails can cross one plank.
  • A cassette is a module: Cassette W by the baffle length, laid whole by
    the panel engine, so partial coverage costs a whole module. Baffles are
    cassettes times the baffles each holds; two end caps per baffle; backer
    rails and their connections are inside the module.

The dock

  • Two floating surfaces instead of four: what you are doing (read tools,
    the scope, Take off or the tools and Done) and where you are (sheet, zoom,
    scale). Reassessed against Fluent's CommandBar.
  • Four density tiers of drawing width. Labels on the tools at Spacious;
    every tier sheds into that surface's "…" — a command is never unreachable,
    and the dock never wraps.
  • The tool in hand is a fill with its glyph in the accent, not a navigation
    pill. Done takes the slot Take off held. The scope pill names its state —
    no round, add a scope, choose a scope — and with no drawing the read tools
    and Take off are disabled in place. A pinned calibration dims the work
    surface.
  • Picking a scope in the dock opens it in the sidebar.

Windows' materials

  • Mica shows through the title bar and both sidebars. The window was
    transparent and the panes painted nothing, and still the chrome was a warm
    grey: the vendored design system painted html underneath. Fixed.
  • Every transient surface — menus, flyouts, the switcher, the search chooser,
    the prompt's flyouts, the dock, toasts — is acrylic: a tint, a 40px blur, a
    grain.
  • Hover, selected, raised and divider fills are Fluent's alpha whites, so a
    selected row is the surface lifted, not a grey box on the wallpaper.
  • The accent is the Windows accent, on every accent-coloured thing. It read
    as Windows' default blue on machines with another accent because the same
    vendored block shadowed the stamped value. Fixed, and re-read on focus.

The surfaces built to approved boards

  • The estimates sidebar, rebuilt: round list, a one-page scope with
    Parts first, Setup and Markups beneath, and the InfoBar that says what the
    number needs.
  • The start window: a filterable list of recent projects with pin, inline
    rename, locate for a moved folder and a context menu; "Open a project
    folder" is the primary card. A drawing opens for viewing without a
    project
    : the first markup action asks for the drawing's project folder
    before it does anything.
  • The project switcher is a flyout: the current project with rename,
    reveal and context window, a filterable recent list, Open another and
    Start page.
  • Search highlights ask which scope first. A highlight is a markup and
    a markup belongs to a scope; with none chosen, Highlight opens the chooser
    instead of landing in whatever scope was last active. Hits are grouped by
    sheet, the open drawing first.
  • Settings is one centred page of cards with an On/Off word, a Reset
    glyph and an About that says where the accent came from.
  • The prompt reads as a Raycast: one field, grouped results, the action
    bar, and the no-scale warning names its sheet.
  • One icon dictionary: Fluent's families, Regular at rest and Filled
    when current, across the rail, the dock and the sidebar.
  • Contents and Thumbnails are greyed until a drawing is open; opening a
    drawing switches the rail to Contents.

The control surface (2026-09-11 plan, all seven phases)

  • The prompt does the thing, in the prompt, and asks rather than assumes.
  • Lengths read as an estimator writes them: 7′ 2 7/8″, not 7.239583.
  • Layout drawing on the sheet; the PDF's own markups as objects; a trace of
    the region; the app icon; recent projects with settings.

Bug review of 2026-09-10 (Kenneth's 24 items, five phases)

  • Cutouts clip to the areas they open. Fit sheet, search hits across
    documents, the start screen on launch. Drawing and selection: a Select tool
    for marquee selection, and the tools stay off the keyboard's text fields.
    Setup and quantities, project and search, and the PDF's foreign markups.

Tooling

  • A DevTools driver that refuses to drive anything but REDBEAM. A shell
    harness that reaches every surface, including the highlight gate, without
    a real project. Dead stylesheet rules pruned by a script that reads the
    components.

REDBEAM 0.2.1 — what the live test found, fixed

Choose a tag to compare

@testusercar testusercar released this 08 Sep 19:20

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.2.1_x64-setup.exe
A Snapdragon / ARM device REDBEAM_0.2.1_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, need no administrator rights, and upgrade
0.1.0 or 0.2.0 in place.

The architecture in each filename is real, checked against the PE header of the
application binary: 0xAA64 for arm64 and 0x8664 for x64.

What changed since 0.2.0

Everything the live test of the installed 0.2.0 build on a 693-document set
turned up (docs/AUDIT-2026-09-04.md, "Live test"):

  • Opening a folder inside a project no longer creates a second database in
    it.
    The automation bridge's open now goes through the same project
    resolution as the picker.
  • The command palette keeps focus through a step chain, and Escape
    cancels it outright; Backspace on an empty field is the way back a step.
  • "This sheet has no scale" waits for a sheet instead of showing on the
    start of every project.
  • Indexing shows its progress: a determinate ring behind the collapsed
    Search tab, the count and a foot bar on the expanded tab, and a bar with the
    numbers in the Search pane's footer. No spinner over the expanded tab.
  • A round's scope rows and totals are right after a reopen with no sheet
    visited: the project's markups load as soon as the store opens.
  • Switching or closing a project releases its database once the last
    window on it has let go, so its files can be moved or removed while the app
    runs.

The full list is in CHANGELOG.md.

Known gaps

  • One item from the live test is still unproven in the installed build:
    whether the webview delivers Escape to the palette at all. It is one
    keypress to check in this build.
  • The page-scale flyout is still two flyouts (the picker and the region
    list); the mockup's single flyout is open as register entry C4.
  • Accuracy against a human estimator's takeoff has not been measured.
  • No update endpoint is configured. The updater says so rather than claiming
    this copy is current.

REDBEAM 0.2.0 — the palette, the WinUI 3 shell, two bug lists

Choose a tag to compare

@testusercar testusercar released this 05 Sep 01:22

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.2.0_x64-setup.exe
A Snapdragon / ARM device REDBEAM_0.2.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, and
they upgrade a 0.1.0 install in place.

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 changed since 0.1.0

The shell is WinUI 3 in its materials and metrics. System fills for every
warning, note and toast; acrylic flyouts with the surface stroke; the 3×16
selection pill; the black-and-white focus pair; Compact row heights; the
Windows accent on primary actions; Fluent UI System Icons throughout.

The scope pane is rebuilt. A scope is its headline measures and one status
line, then Parts, Setup and Markups. There is no separate bill of materials:
a scope's parts are its Parts page, and the round's exports sit in the
round's header menu with Rename, Duplicate and Delete. The estimate also
exports as a branded PDF, CSV or TSV through a native Save As.

Settings is a full-screen NavigationView with a search box, settings
cards, expanders, and an About page.

The command palette can drive the whole app. Prefixes (> # : @
/ = ~, ? lists them), recents, argument steps typed into the same
field, toggles that flip and stay, refusals that keep the palette open with
the nearest thing that works, and every verb: scale for a sheet, every sheet
or a series; rounds and scopes end to end (add, configure, rename, product,
counts, duplicate, archive, restore); exports; tools; commit; undo and redo;
every setting as a switch. Aliases on every command, so "hand" finds Pan.

Fixed. Opening a drawing as a project and then its parent no longer
breaks both windows (one database connection per project). A project opens
on the Files pane, now a nested folder tree. The wheel scrolls and Space or
the middle button pans. Page text is indexed for the whole project on open,
with progress on the Search tab. Rows truncate instead of wrapping. The
layout below the 960px window minimum degrades instead of collapsing.

The full list is in CHANGELOG.md.
The design register is docs/FLUENT-GAPS.md; the functionality audit is
docs/AUDIT-2026-09-04.md.

Known gaps

  • The palette's verbs, the per-project database connection, the indexer and
    the exports were verified in the browser build and by the test suites, not
    yet on a real project in the installed app. Treat this build as the one
    that gets that run.
  • The page-scale flyout is still two flyouts (the picker and the region
    list); the mockup's single flyout is open as register entry C4.
  • Accuracy against a human estimator's takeoff has not been measured.
  • No update endpoint is configured. The updater says so rather than claiming
    this copy is current.

REDBEAM 0.1.0 — Windows Fluent shell

Choose a tag to compare

@testusercar testusercar released this 04 Sep 16:28

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.