M1.4: desktop bridge: engine events to the window, folder picker, live project tree
The desktop host publishes every engine event, from commands and from a
pump thread that calls Engine::pump_vfs every 100 ms, to control channel
subscribers and to the window as the Tauri event engine://event, in engine
order. ui/src/ipc.ts gets a typed onEngineEvent; its first subscription
calls engine_ready, and the host replays the current project and buffers,
so a project opened from the command line (lutra-desktop --control PORT
PATH) reaches the UI. project.openDialog returns Effect::PickFolder; the
host shows the native folder picker (tauri-plugin-dialog, licence checked)
and opens the choice, one picker at a time, cancel is not an error.
Capabilities shrink to event listen/unlisten.
Contract fix: the M1.5 project UI assumed shapes the engine does not use.
engineEvents.ts now translates engine events ({kind: projectOpened, ...})
and project.children results ({dir, entries, truncated}) into the UI types,
keeping role and truncated; the store maps listings through
toTreeEntries() and the project tests use the real engine shapes.
Verified in the running app on Windows 11: tree of a project given on the
command line, expanding src, a file created on disk appearing live, the
folder picker opening one dialog and opening the chosen folder.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
parent
69130d1efb
commit
dd98636de4
23 changed files with 751 additions and 99 deletions
10
ROADMAP.md
10
ROADMAP.md
|
|
@ -2,7 +2,7 @@
|
|||
|
||||
**Stage: pre-alpha (foundation done)** · next: M1 editor and project; 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-14 · **Last updated:** 2026-10-14 · **Change:** minor (M0 done, first estimates) · **Target:** JetBrains PhpStorm 2026.x, described from public documentation only
|
||||
> **Last reviewed:** 2026-10-14 · **Last updated:** 2026-10-15 · **Change:** minor (project tree works against the engine) · **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).
|
||||
|
||||
|
|
@ -13,7 +13,7 @@ Lutra is a clean-room, open-source PHP IDE with a Rust core and a Tauri + Vue in
|
|||
| | Value | Kind |
|
||||
|---|---|---|
|
||||
| **Feature breadth** (PhpStorm's actions, tool windows, languages, integrations exist) | **0%** | measured |
|
||||
| **Feature depth** (weighted by use, scored by behaviour) | **0%** | measured |
|
||||
| **Feature depth** (weighted by use, scored by behaviour) | **~0.5%** (Project view 8% × weight 6) | estimated |
|
||||
| **To MVP (M3)** | **~190 h** (M1 ~60 h, M2 ~50 h, M3 ~80 h) | estimated |
|
||||
| **To full parity** | **~3,300 h** (range 2,000–5,000 h) | estimated |
|
||||
|
||||
|
|
@ -25,7 +25,7 @@ Dimension hours overlap: language, framework and tooling hours are part of the f
|
|||
|
||||
| Dimension | % | One agent (h) | Doc |
|
||||
|---|---:|---:|---|
|
||||
| Features (depth) | 0% | ~2,930 | [target-app-parity.md](docs/target-app-parity.md) |
|
||||
| Features (depth) | ~0.5% | ~2,930 | [target-app-parity.md](docs/target-app-parity.md) |
|
||||
| UI/UX fidelity | 0% | ~150 on top of features | [ui-parity.md](docs/ui-parity.md) |
|
||||
| PHP language support | 0% | ~920 (in features) | [language-parity.md](docs/language-parity.md) |
|
||||
| Frameworks (Symfony, Laravel, Shopware, WordPress) | 0% | ~300 (in features) | [framework-parity.md](docs/framework-parity.md) |
|
||||
|
|
@ -42,7 +42,7 @@ Stability 5%: no-panic lints, the engine guard and a fuzzed control protocol exi
|
|||
| Area | % | One agent (h) |
|
||||
|---|---:|---:|
|
||||
| Editor core (buffers, undo, multi-caret, folding, soft wrap) | 0% | ~120 |
|
||||
| Project view, VFS, file watching | 0% | ~40 |
|
||||
| Project view, VFS, file watching | 8% (est.) | ~40 |
|
||||
| Navigation (go to class/file/symbol, recent files, structure) | 0% | ~120 |
|
||||
| Search and replace (in file, in project, structural) | 0% | ~80 |
|
||||
| Code completion | 0% | ~250 |
|
||||
|
|
@ -77,6 +77,7 @@ All hours estimated. Weights, evidence and the missing items per area: [target-a
|
|||
|
||||
| Date | What landed |
|
||||
|---|---|
|
||||
| 2026-10-15 | M1 so far: text buffer, VFS with native watching, engine workspace (files, buffers, edit protocol, events), desktop bridge: open a folder by picker or command line, browse it in the project tree with live updates from disk. |
|
||||
| 2026-10-14 | M0 foundation: Cargo workspace with layered crates, no-panic lints with a self-test, `cargo xtask ci` (fmt, clippy, tests, layers, assets, clean-room, licences, frontend lint/typecheck/tests), Vue frontend, command registry with panic guard (`app.about`, `app.quit`), JSON control channel, Tauri window themed from Rust tokens, CI workflow. First estimates. |
|
||||
| 2026-10-13 | Project started: name, conventions, agent rules and progress docs. |
|
||||
|
||||
|
|
@ -84,5 +85,6 @@ All hours estimated. Weights, evidence and the missing items per area: [target-a
|
|||
|
||||
| Date | Change | Summary |
|
||||
|---|---|---|
|
||||
| 2026-10-15 | minor | Feature depth above 0%: project tree runs against the engine (M1.4) |
|
||||
| 2026-10-14 | minor | M0 done; MVP and parity estimates; stability and agent automation scored |
|
||||
| 2026-10-13 | major | Initial roadmap |
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue