feat(editor): dictation mic cue + how-to (#14)#67
Draft
ChrisPelatari wants to merge 2 commits into
Draft
Conversation
Approved brainstorming output for #14: a docs how-to + a subtle mdi-microphone cue (no speech engine — dictation already works via the OS: Android keyboard mic, Windows Win+H). Decisions: real mdi-microphone icon (Material icon font, subsetted) on BOTH platforms; tapping focuses the editor (existing window.PostXING.focus()) and shows a transient platform-specific hint ("Press Win+H" / "Tap the mic on your keyboard"). Plus docs/dictation.md.
Dictation already works via the OS (Android keyboard mic, Windows Win+H); #14 is about discoverability. Adds a real mdi-microphone cue that focuses the editor and shows a transient platform hint, plus docs/dictation.md. No speech engine. - subsetted Material Design Icons font (microphone glyph U+F036C only, ~840 bytes, not the 1.3 MB webfont) registered as "MaterialIcons" - Windows: shapes:Path mic in the status bar (theme-reactive Fill, matches the preview/sync icon convention); Android: a primary mic ToolbarItem (FontImageSource) - tap -> window.PostXING.focus() + a self-contained fade-in/out hint ("Press Win+H" / "Tap the mic on your keyboard"); no new dependency - DictationHints.For(platform) — the one pure, unit-tested seam (3 tests) - docs/dictation.md: Win+H (Windows) and keyboard mic (Android) how-to Windows head builds 0/0; ViewModels 254 green. Android on-device verification is BLOCKED by the build host's memory (#57): the Dell OptiPlex 3060 (8 GB RAM, fixed 6 GB page file) can't give the Android build JVM commit headroom — needs the RAM bump / page-file fix before the Android glyph + cue can be verified on panther.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resolves #14 (pending Android on-device verification — see below).
Brainstormed → spec'd → implemented. Dictation already works via the OS (Android keyboard mic, Windows Win+H); this adds discoverability, not a speech engine.
U+F036Conly, 840 bytes, not the 1.3 MB webfont).shapes:Pathmic in the status bar (theme-reactiveFill, matches the existing preview/sync icon convention). Android: a primary micToolbarItem(FontImageSource).window.PostXING.focus()+ a self-contained fade-in/out hint (Press Win+H/Tap the mic on your keyboard) — no new dependency.DictationHints.For(platform)— the one pure, unit-tested seam.docs/dictation.mdhow-to.Verification: Windows head builds 0W/0E; ViewModels 254 green (incl. 3 DictationHints tests). Android on-device verification is blocked by the build host's memory (#57): the Dell OptiPlex 3060 (8 GB RAM, fixed 6 GB page file) can't give the Android build JVM commit headroom. Draft until the Android mic glyph + cue are verified on panther once the host memory is addressed.
🧠 superpowers brainstorming → approved spec (
docs/superpowers/specs/2026-06-10-dictation-discoverability-design.md).🤖 Generated with Claude Code