M1.9b: settings dialog with search

settings.open (Mod+,) opens a dialog built from settings.list: sections,
controls by type (select, number with min/max, switch), catalog labels
and descriptions, search over label, description, key and section, Reset
to default, inline errors, live updates on settingsChanged. The theme
picker switches at once; editor.fontSize drives --lt-font-size-editor
through a token override that survives theme switches. Focus trap,
Escape closes. Finishes M1.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
danny 2026-10-16 21:13:04 +02:00
parent db34e2ca52
commit 523d7f684f
17 changed files with 1751 additions and 36 deletions

View file

@ -1,20 +1,20 @@
# Lutra Roadmap
**Stage: pre-alpha (M1 in progress)** · next: the rest of M1 (settings dialog), then M2 syntax and search; alpha when the six core workflows work end to end (see [docs/roadmap.md › Alpha gate](docs/roadmap.md#alpha-gate))
**Stage: pre-alpha (M1 done)** · next: M2 syntax and search; alpha when the six core workflows work end to end (see [docs/roadmap.md › Alpha gate](docs/roadmap.md#alpha-gate))
> **Last reviewed:** 2026-10-15 · **Last updated:** 2026-10-16 · **Change:** minor (M1.8: command palette and keymap) · **Target:** JetBrains PhpStorm 2026.x, described from public documentation only
> **Last reviewed:** 2026-10-15 · **Last updated:** 2026-10-16 · **Change:** minor (M1.9b: settings dialog; M1 done) · **Target:** JetBrains PhpStorm 2026.x, described from public documentation only
Lutra is a clean-room, open-source PHP IDE with a Rust core and a Tauri + Vue interface, targeting the PhpStorm workflow. Agents can drive all of it over MCP, the `lutra` CLI and a JSON control channel. This page is the summary; the evidence is in [`docs/target-app-parity.md`](docs/target-app-parity.md) and the work list in [`docs/gaps.md`](docs/gaps.md).
**Why pre-alpha:** M0 built the foundation (workspace, quality gate, command registry with panic guard, control channel, a themed window). M1 so far lets you open a folder, browse it in the project tree and edit and save files in tabs, but as plain text: no PHP feature (highlighting, completion, navigation) exists yet. M1–M3 deliver the MVP.
**Why pre-alpha:** M0 built the foundation (workspace, quality gate, command registry with panic guard, control channel, a themed window). M1 lets you open a folder, browse it in the project tree, edit and save files in tabs, get unsaved text back after a crash, run every command from a palette and change settings and the theme in a settings dialog, but as plain text: no PHP feature (highlighting, completion, navigation) exists yet. M1–M3 deliver the MVP.
## Headline numbers
| | Value | Kind |
|---|---|---|
| **Feature breadth** (PhpStorm's actions, tool windows, languages, integrations exist) | **<1%** (project tool window, editor tabs; no inventory to count against yet) | estimated |
| **Feature depth** (weighted by use, scored by behaviour) | **~1.6%** (Editor core 9% × weight 12, Project view 8% × weight 6, Settings 4% × weight 1, of 101) | estimated |
| **To MVP (M3)** | **~20 h** (M1 ~6 h of which 2.5 h done, M2 ~5 h, M3 ~8 h); was ~190 h before calibration | estimated (×0.1 from cycle C1) |
| **Feature depth** (weighted by use, scored by behaviour) | **~1.6%** (Editor core 9% × weight 12, Project view 8% × weight 6, Settings 7% × weight 1, of 101) | estimated |
| **To MVP (M3)** | **~13 h left** (M1 done: C1 2.5 h measured, C2 time in the cycle review; M2 ~5 h, M3 ~8 h); was ~190 h before calibration | estimated (×0.1 from cycle C1) |
| **To full parity** | **~330 h** if cycle C1's speed holds (range 300–3,300 h; deep areas such as type inference and inspections have no data yet) | estimated |
Hours are agent wall-clock hours for one agent. M0 took about 2 h of active agent time (measured from the session, excluding toolchain installation and waiting for owner decisions). Later milestones are estimated far more conservatively per line of code, because editor, language and UI work need integration, debugging and visual checks that the foundation did not. Estimates are recalibrated after each cycle from task start times and commit timestamps. Cycle C1 (M1.1–M1.6) took 2.5 h of agent time for 37 h estimated (factor 0.07); M1–M3 hours are scaled by ×0.1 since then, and the per-area hours below are the raw first estimates (multiply by ~0.1 for the calibrated value). PhpStorm is **not** inspected: the clean-room rule in [`AGENTS.md`](AGENTS.md) forbids it, so everything is measured from our code against public documentation.
@ -60,7 +60,7 @@ Stability 8%: no-panic lints, the engine guard, a fuzzed control protocol and a
| HTTP client | 0% | ~60 |
| Web languages (JS/TS, Vue, CSS, Twig, Blade) | 0% | ~200 |
| Docker and remote | 0% | ~120 |
| Settings, keymaps, themes | 4% (est.) | ~60 |
| Settings, keymaps, themes | 7% (est.) | ~60 |
| Plug-ins and ecosystem | 0% | ~120 |
| AI features | 0% | ~60 |
@ -68,15 +68,15 @@ All hours estimated. Weights, evidence and the missing items per area: [target-a
## Upcoming
1. **M1 editor and project (~6 h, 2.5 h done):** open folder, project tree, tabs, editor, save and recovery, command palette, settings, themes.
2. **M2 syntax and search (~5 h):** highlighting, file structure, find in files, go to file/class/symbol.
3. **M3 language server, terminal and CLI (~8 h):** completion, diagnostics, go to definition via Phpactor; terminal; `lutra` CLI and MCP. **MVP.**
4. **Then:** Git (M4), debugger, tests and Composer (M5), own indexer and frameworks (M6).
1. **M2 syntax and search (~5 h):** highlighting, file structure, find in files, go to file/class/symbol.
2. **M3 language server, terminal and CLI (~8 h):** completion, diagnostics, go to definition via Phpactor; terminal; `lutra` CLI and MCP. **MVP.**
3. **Then:** Git (M4), debugger, tests and Composer (M5), own indexer and frameworks (M6).
## Progress log
| Date | What landed |
|---|---|
| 2026-10-16 | M1.9b, M1 done: a settings dialog (`Mod+,`) built from the engine's settings, with search, a control per type, reset to default and inline errors; changes apply at once and follow edits from agents live; the theme picker switches at once and the editor font size applies to the editor. |
| 2026-10-16 | M1.8: a command palette (`Mod+Shift+P`) finds every command by fuzzy match, recent ones first, with shortcuts shown and unavailable ones dimmed; one global keymap serves engine and UI commands (`Mod+1` toggles the project tree); agents can trigger UI commands over the control channel. |
| 2026-10-16 | M1.12: errors and notices reach the user as toasts instead of stderr: a corrupt settings file or recovery entry, a folder that cannot be opened (also with unsaved changes when switching projects), stopped file watching and failed commands without their own UI. Info toasts go away after 5 s, warnings and errors stay. |
| 2026-10-16 | M1.7: unsaved text survives a crash. Dirty buffers are journaled about a second after the last edit; the next open offers them in a restore dialog (restore all, selected, or discard), with line endings and BOM kept. |
@ -91,6 +91,7 @@ All hours estimated. Weights, evidence and the missing items per area: [target-a
| Date | Change | Summary |
|---|---|---|
| 2026-10-16 | minor | M1.9b: M1 done, stage line, Settings row 7% (est.), progress log |
| 2026-10-16 | minor | M1.8: progress log, agent automation note (scores unchanged) |
| 2026-10-16 | minor | M1.12: progress log (headline unchanged) |
| 2026-10-16 | minor | M1.7: Stability 8%, Editor core 9%, feature depth ~1.6% (with Settings 4% from M1.10) |