Move the flame_studio debugging features to flame_devtools

Aperta
  • Qualcosa non va?
#4,176 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
dart, flutter
Ambito
game-dev

Direzione di ricerca

This is an umbrella proposal; its listed features are split into independent issues #4168–#4175. For context, inspect the prior implementation at commit 50f00635b in packages/flame_studio and compare it with flame_devtools; start with one of the linked child issues. Done means the selected feature is available in flame_devtools; issue #4175 additionally needs a design decision.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement
Problem to solve

flame_studio and flame_devtools have grown into two separate debugging tools for running Flame games. They overlap on game loop controls, the component tree, debug mode and transform editing, so features end up split between them.

flame_devtools is the better home: it ships with flame, needs no change to how a game is started, and already has features flame_studio lacks, such as component snapshots, the image cache panel, overlay controls and the behavior tree viewer.

Proposal

Move what flame_studio has and flame_devtools doesn't into flame_devtools. The issues below can be worked on independently.

Small

  • #4168 Anchor picker
  • #4169 Rendering properties (visibility and opacity)
  • #4170 TextComponent text
  • #4171 Component lifecycle state

Medium

  • #4172 Number editing (degrees, drag-to-scrub, tooltips)
  • #4173 Live updates
  • #4174 Extensible component inspectors

Large

  • #4175 Viewport tools (select, move, rotate, scale), which needs a design decision first
Feature comparison
Feature flame_studio flame_devtools
Pause and resume Yes Yes
Step frame Fixed 1/60 s Custom step time, forward and backward
Component tree Live Manual refresh
Priority, position, size, scale, angle Yes Yes
Debug mode Always the subtree One component or the whole game
Anchor, visibility, opacity, text, lifecycle state Yes No
Pluggable inspectors Yes No
Select and transform in the game view Yes No
Snapshots, image cache, overlays, behavior trees No Yes
More information

The current flame_studio code is going to be replaced by a different tool, so the issues describe the behavior directly rather than linking to source files. Its last state before that change can be found at commit 50f00635b, in packages/flame_studio.

Closes: #2319

Lingua principale
Dart
Stelle
10.8k
Fork
1.1k
Merge medio
1g 21h
PR unite (30g)
53

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di flame-engine/flame

Tutte le issue di flame-engine/flame

Issue simili

Altre issue su Dart

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.