ChrisTitusTech / ChrisTitusTech/warframe-linux

R02: P3: live capture and reward panel

Open
#8 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement phase:P3
Dominant language
Go
Stars
4
Forks
1
Avg merge
7m
Merged PRs (30d)
4

Description

Go implementation tracking epic

Selected stack: Go + Wails v2 + React/TypeScript + SQLite. Implementation starts on the next machine. Each child below is a separate PR; do not implement this epic in one PR.

Child tasks

  • R02a: Wayland live capture adapter
    • Merged prerequisites: R01b, F02a.
    • Acceptance: R5/R6: selected portal source, bounded frames, stop/revoke/cancel cleanup and no retained images; real desktop evidence on claimed Wayland targets.
  • R02b: X11 capture adapter and fallback
    • Merged prerequisites: R01b, F02b.
    • Acceptance: R5/R8: explicit supported X11 capture; unavailable capability yields image-import/normal-window fallback; manual evidence and cleanup tests.
  • R02c: Capture controls and reward lifecycle
    • Merged prerequisites: R02a, R02b.
    • Acceptance: R5/R8: user starts/stops scan; no duplicate/stale reward sessions; memory/latency and focus evidence; real game verification only when separately authorized.

Workflow

See TASKS.md, ROADMAP.md, and CONTRIBUTING.md. Aim for 100-400 handwritten changed lines per PR; split above 600 unless inseparable. Merge prerequisites before dependents. Update task evidence and this checklist after each completed PR. Close this epic only when every child passes; optional work can remain deferred.

All tasks are not started. Live game access and publication/merge actions follow the user's explicit authorization. The planning handoff does not claim runtime validation.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with TASKS.md, ROADMAP.md, and CONTRIBUTING.md, then verify prerequisites R01b, F02a, and F02b before choosing a child task. Treat R02a, R02b, and R02c as separate PRs; use each listed acceptance criterion and desktop or manual evidence as the definition of done, and close the epic only after all children pass.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, react, sqlite, typescript
Domain
backend, desktop, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.