Skip to content

feat: redesign settings and add cross-platform transparency#234

Open
cmdr-chara wants to merge 2 commits into
alecdotdev:masterfrom
cmdr-chara:feat/settings-workbench-redesign
Open

feat: redesign settings and add cross-platform transparency#234
cmdr-chara wants to merge 2 commits into
alecdotdev:masterfrom
cmdr-chara:feat/settings-workbench-redesign

Conversation

@cmdr-chara

@cmdr-chara cmdr-chara commented Jul 22, 2026

Copy link
Copy Markdown

Summary

  • redesign the Settings window around one shared Markpad workbench visual system
  • add searchable, draggable, and resizable settings with consistent native controls and live font previews
  • add configurable application/editor toolbars with ordering, visibility, and placement controls
  • add whole-window solid/translucent surfaces with persisted opacity, backdrop dimming, and blur preferences
  • align the titlebar overflow and home menus, preserving translated labels and shortcut columns
  • complete the new settings copy for every supported language

Screenshots

Editor

Editor settings

Appearance

Appearance settings

Toolbars

Toolbar settings

Platform behavior

  • Windows uses the native blur effect when translucency and blur are enabled
  • macOS uses the under-window background effect
  • Linux keeps alpha transparency and backdrop dimming, while native blur stays disabled because support depends on the compositor
  • solid mode remains fully painted by the web UI; the installer window remains opaque

Validation

  • npm run test:workflows — 33/33 passing
  • npm run build — passing
  • cargo check --manifest-path src-tauri/Cargo.toml — passing
  • git diff --check — passing
  • npm run check — no new diagnostics; still reports the existing unused @ts-expect-error in vite.config.js and the existing timer type mismatch in MarkdownViewer.svelte

Notes

The appearance panel now uses the same group, row, control, focus, and spacing rules as every other settings category instead of maintaining a separate custom layout.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant