Swap @ng-icons/mynaui for @ng-icons/tdesign-icons (34.0.0, the release
matching @ng-icons/core), drawn at TDesign's native stroke. Each former
mynaui name maps to one TDesign name everywhere it was used; the unused
ArrowLeftRight is dropped. The options button's ellipsis goes from 1.5rem
to 0.8rem: TDesign's dots span 18 of 24 units against mynaui's 8, so this
keeps today's footprint.
Co-Authored-By: Claude <noreply@anthropic.com>
Groundwork for the continuous interface scale (a root font-size lever): every
size the UI derives from must be root-relative, or it freezes while the rest
grows. Gate for this commit: at the default 16px root the app renders
pixel-identical to before — every conversion is exact (11px = 0.6875rem …).
- The 8 panel-chrome tokens in styles.css: px -> rem, and the data-text
compact/large tiers are DELETED — a continuous scale replaces discrete
tiers. Same for --w7-fs (12px -> 0.75rem) and the win7 --radius (5px ->
0.3125rem, still landing rounded-md exactly on --w7-el-bdr's 3px).
--radius-sm/md subtrahends: px -> rem, or corners would sharpen as the UI
grew.
- All 93 text-[11px]/text-[10px] arbitraries -> rem equivalents, plus the two
inline padding:24px empty-state cells in the 7like file panel.
- 7like.css gains a scale bridge in skinfix: 7.css is 370 px values with zero
rem, and --w7-font reaches only 15 rules' TYPOGRAPHY — under a root lever
win7 text would grow inside boxes frozen at 23px/14px/15px. The bridge
re-expresses 7.css's size vars and its hardcoded box metrics (buttons via
.w7-btn only, inputs, table rows/headers, title-bar controls, menu items,
tabs, the 10pt check glyph) in rem at identical scale-1 pixels. 1px
hairlines and focus rects stay px deliberately — crisp at any scale, and
the tr border exists precisely to stop selection shifting rows.
- Two skinfix traps found while writing it, one by reasoning and one by
pixels: (a) NO blanket `.win7 button` restatement — skinfix outranks the
skin-layer neutralizer that strips 7.css's 75x23 metrics off the ~84 icon
buttons, so a blanket rule would re-inflate them all; (b) restating a base
rule in skinfix also outranks 7.css's own VARIANTS of it by layer — the
title-bar rule silently shrank the close button from 48px to 29px until the
harness pixel diff caught it, and the active tab's padding-bottom needed
the same treatment. Both variants are restated alongside their base rules.
- TS px constants that mirror rem CSS are the latent-bug half of this work:
both context menus' flip/clamp math converts through a new @core/metrics
remPx() helper reading the LIVE root font-size (the shadlike menu's
MENU_W=224 diverged from its w-56 box the moment scale != 1; the 7like
menu's [style.width.px] pinned the box at 200px while text grew — it now
binds width in rem, so math and box cannot disagree). The editors'
cachedCharWidth is now keyed on the computed font string, self-invalidating
under any font change, and both || px fallbacks derive from the element's
font size instead of assuming a 16px root.
Verified: tsc + build clean; modern and win7 live captures and the harness
all diff to zero against pre-change baselines in their opaque regions (the
harness to exactly zero end to end; modern's only delta is the native GTK
titlebar focus state; win7's is the translucent Aero corner over the
desktop).
Co-Authored-By: Claude <noreply@anthropic.com>
Both UIs now live side by side. The 18 modern component files come straight
from `git show main:<path>` — recovered, not rewritten, which is possible
because main's tip IS the merge base of this branch. There is no title-bar
among them: that component is win7-only, since the modern skin defers to the
native window frame.
Their imports were rewritten to @core the same way stage 1 did, leaving only
skin-internal relative imports behind. Added skins/shadlike/index.ts exporting
SHAD_ROOTS with the same shape as SEVEN_ROOTS, so main.ts can select a tree
without knowing either skin's internals.
Restored the skin axis in core/platform.ts, deleted in fe028a9 and needed
again by the modern tree: __APP_SKIN on the Window global, APP_SKIN,
IS_WIN7_CHROME, and IS_MAC_CHROME = IS_MAC && !IS_WIN7_CHROME. That last one
is what reserves pl-24 for the macOS traffic lights in the fused hiddenInset
header — and correctly stops reserving it under win7, where titleBarStyle
'hidden' removes the traffic lights entirely.
The tree is not reachable yet; the build is the gate. I checked that the gate
is real rather than assuming it: injecting a type error into an unreferenced
shadlike file does fail `bun run build:ui`, so ngtsc type-checks the whole
program including components nothing imports. Without that check, "the build
passes" would have proven nothing about 18 files no one references.
win7 remains pixel-identical to the pre-refactor baseline.
Co-Authored-By: Claude <noreply@anthropic.com>
jgamboaandClaude