Roadmap: native GPU terminal on Windows and Linux (tracking)

Aberta
#249 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
8/100
Tipo de issue
Funcionalidade
Clareza
Precisa de esclarecimento
Status de atividade
Ativa
Stack de tecnologia
rust
Domínio
desktop-dev

Direção de pesquisa

This is a tracking issue, not a work item: it maps the whole native GPU terminal programme and delegates each step to a child issue (#239-#248, plus shared-engine #252-#256). Start by reading docs/terminal.md#roadmap-windows-and-linux and discussion #237 for the design and measurements, then pick a single unchecked phase issue rather than this one. Done here means every phase issue is closed and the terminal is default on Windows; a newcomer should contribute to a phase instead.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

area: terminal priority: 1 high status: confirmed type: feature

Tracking issue for the native GPU terminal on Windows 10 1809+ / Windows 11 and Linux, at the macOS level. Design, research and measurements: discussion #237. Roadmap page: docs/terminal.md#roadmap-windows-and-linux.

Decisions

Layer Decision
Windows renderer native D3D11 (measured: wgpu DX12 +65 MB, ~2.5× device time); one shader source (term.wgsl → naga → HLSL SM 5.0)
macOS / Linux renderer wgpu (Metal / Vulkan)
No GPU, VM, RDP D3D11 WARP, then xterm.js
Windows PTY own ConPTY layer + pinned bundled conpty.dll/OpenConsole.exe, self-test, inbox fallback
Windows text DirectWrite into our atlas
Windows composition child HWND first, then DirectComposition + WebView2 visual hosting
Linux X11 child window; Wayland on xterm.js until wry GTK4

Phases

  • #239 Phase 0: benchmark harness + baselines (macOS reference, Windows, ConPTY, VMs/RDP) (absorbs #110; extends the macOS numbers already in docs/terminal.md "Performance")
  • #240 Phase 1: own ConPTY layer
  • #241 Spike: child HWND next to WebView2
  • #242 Phase 2: D3D11 backend + term/win.rs
  • #243 Phase 3: native data path, on-demand rendering
  • #244 Phase 4: DirectWrite, IME, UIA, DPI
  • #245 Phase 5: DirectComposition + WebView2 visual hosting
  • #246 Phase 6: default on Windows
  • #247 Phase 7: Linux X11
  • #248 Phase 8 (optional): WSL without ConPTY

Shared engine (all platforms)

  • #252 single pass over PTY bytes before the parser
  • #253 decouple PTY read from parse
  • #254 release GPU resources of hidden terminals
  • #255 spike: libghostty-vt as VT core
  • #256 idle compression of cold scrollback
flowchart LR
  P0[#239 Phase 0] --> P1[#240 ConPTY]
  P0 --> S[#241 HWND spike] --> P2[#242 D3D11]
  P1 --> P3[#243 data path]
  P2 --> P3 --> P4[#244 text/IME/UIA] --> P6[#246 default]
  P2 --> P5[#245 DComp] --> P6
  P2 --> P7[#247 Linux X11]
  P1 --> P8[#248 WSL]

Labels: every issue of this roadmap is area: terminal + milestone Roadmap: native GPU terminal (Windows & Linux).

Linguagem predominante
Rust
Estrelas
3
Forks
1
Merge médio
9h 51min
PRs com merge (30d)
310

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de codeatlasdev/atlas

Todas as issues de codeatlasdev/atlas

Issues semelhantes

Mais issues de Rust

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.