feat(startup): match gclo splash and Advanced settings #25

New Issue

2026-10-11T14:57:36Z

KofTwentyTwo commented

2026-10-11 14:57:36 +00:00

(Migrated from github.com)

Add the branded startup splash and Advanced settings requested by the owner, matching gclo while using published AppKit 0.1.0.

Acceptance:

Show the branded vector logo, application name/tagline, build identity, author credit and activity strip on initial launch; fade away without opening/closing a separate splash window.
Settings → Advanced contains a native Show splash screen at startup toggle and Splash duration (milliseconds) NumberBox, 500–30000 ms with 250 ms steps, matching gclo.
Retain saved choices across restarts and synchronize them across open readers without overwriting unrelated preferences.
Move startup update-check preferences from View into Advanced; changes apply on the next launch.
Test actual enabled/disabled startup and duration persistence; retain launch and distribution evidence before closing.

The shared AppKit splash is already connected. The earlier review profile disabled it; new work must make the controls discoverable and provide a splash-enabled review build. Production signing and independent review remain separate requirements.

Substantial implementation assistance: Codex (GPT-6).

Add the branded startup splash and Advanced settings requested by the owner, matching gclo while using published AppKit 0.1.0. Acceptance: - Show the branded vector logo, application name/tagline, build identity, author credit and activity strip on initial launch; fade away without opening/closing a separate splash window. - Settings → Advanced contains a native Show splash screen at startup toggle and Splash duration (milliseconds) NumberBox, 500–30000 ms with 250 ms steps, matching gclo. - Retain saved choices across restarts and synchronize them across open readers without overwriting unrelated preferences. - Move startup update-check preferences from View into Advanced; changes apply on the next launch. - Test actual enabled/disabled startup and duration persistence; retain launch and distribution evidence before closing. The shared AppKit splash is already connected. The earlier review profile disabled it; new work must make the controls discoverable and provide a splash-enabled review build. Production signing and independent review remain separate requirements. Substantial implementation assistance: Codex (GPT-6).

KofTwentyTwo commented

2026-10-11 15:05:34 +00:00

(Migrated from github.com)

Implemented locally: published AppKit startup overlay is reused for the branded vector/name/tagline/build/author/activity/fade presentation. Settings → Advanced now contains the gclo splash toggle and duration controls (500–30000ms,250ms steps) and startup update checks, moved out of View. Existing saved durations remain unchanged. Saves change only startup fields in the latest store, then broadcast to all reader baselines and Settings windows without applying CSS drafts. Added an actual native-controls/sibling-save persistence regression; it compiles but has not run.

Fresh owner preview: Review-toolbar-splash.md — MarkdownViewr, PID103040, output artifacts/splash-toolbar-review/bin/x64/Release/net10.0-windows10.0.19041.0/MarkdownViewr.Windows.exe. Its separate review profile enables a5000ms splash and Source, and disables startup update checks. Other owner windows were preserved.

Verification: zero-warning/error full Release build;570 core tests pass,100% measured line coverage; formatting and changed-doc lint pass.79 UI-project cases discovered (66desktop/13filesystem; expected78 per installed channel); actual new desktop/distributed acceptance has not run. Launch/document opening succeeded with no warnings in the profile log. Passive Computer Use inspection was unavailable because its native pipe was not found; no mouse/keyboard input occurred.

The original four staged corrections remain unchanged. Signed commits/push still await the pending1Password ready reply; no signing retry, merge, tag, release or Azure change. System Print handoff, PDF open actions, remaining full PRODUCT parity, standards and exact production-signature proof remain open.

Implemented locally: published AppKit startup overlay is reused for the branded vector/name/tagline/build/author/activity/fade presentation. Settings → Advanced now contains the gclo splash toggle and duration controls (500–30000ms,250ms steps) and startup update checks, moved out of View. Existing saved durations remain unchanged. Saves change only startup fields in the latest store, then broadcast to all reader baselines and Settings windows without applying CSS drafts. Added an actual native-controls/sibling-save persistence regression; it compiles but has not run. Fresh owner preview: `Review-toolbar-splash.md — MarkdownViewr`, PID103040, output `artifacts/splash-toolbar-review/bin/x64/Release/net10.0-windows10.0.19041.0/MarkdownViewr.Windows.exe`. Its separate review profile enables a5000ms splash and Source, and disables startup update checks. Other owner windows were preserved. Verification: zero-warning/error full Release build;570 core tests pass,100% measured line coverage; formatting and changed-doc lint pass.79 UI-project cases discovered (66desktop/13filesystem; expected78 per installed channel); actual new desktop/distributed acceptance has not run. Launch/document opening succeeded with no warnings in the profile log. Passive Computer Use inspection was unavailable because its native pipe was not found; no mouse/keyboard input occurred. The original four staged corrections remain unchanged. Signed commits/push still await the pending1Password ready reply; no signing retry, merge, tag, release or Azure change. System Print handoff, PDF open actions, remaining full PRODUCT parity, standards and exact production-signature proof remain open.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: KofTwentyTwo/MarkdownViewr.Windows#25