Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Example repos that move with fizzy, and a dvui app on fizzy's backend

Aperta
  • Qualcosa non va?
#281 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
12/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
zig
Ambito
build-system, ci-cd, desktop-dev

Direzione di ricerca

This is a tracking issue for several linked efforts, not a single task, so start by choosing one unchecked step and its linked issue. The checklist names VERSION, app/, web/ and .paths for #279, examples/ and CI for #282, and scripts/check-examples.sh for the per-PR build. Done means the chosen item's linked issue or PR is merged and its checkbox can be ticked.

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

Descrizione

Fizzy's examples become two repos that move with fizzy, and the app one grows a plain dvui app on fizzy's backend. That dvui app is the proof that the windowing work belongs in dvui (#243).

  • fizzyedit/example-app: fizzy as a library.
    • zig build run-fizzy -Dshape=minimal|studio|endless is a whole fizzy app in that shape.
    • zig build run-dvui will be dvui's own widgets on fizzy's backend: floats, menus and dialogs as OS windows, Liquid Glass on macOS.
  • fizzyedit/example-plugin: the smallest plugin, the template to copy.

Moving with fizzy.

  • Fizzy's CI builds both repos against each PR's own tree (scripts/check-examples.sh), fetched as a URL dependency would be.
  • An SDK release asks example-plugin to repin, as it asks the store plugins.

Steps

  • Both repos created, with the shapes, the hello plugin (now example-plugin) and the shader plugin (example-app's own).
  • #279: fizzy builds when fetched as a URL dependency. VERSION, app/ and web/ were missing from .paths.
  • #282: fizzy's examples/ removed, with CI building the two repos instead (stacked on #279).
  • example-app repinned from #279's commit to main once #279 merges (fizzyedit/example-app#2), and again to main with the backend package and SDK 0.2.20 (fizzyedit/example-app#3).
  • PLUGIN_DISPATCH_TOKEN scoped to example-plugin too, so the SDK release's repin request reaches it (a repo setting). At 0.2.20 every repin request, to the store plugins too, got HTTP 403: the token reaches none of them.
  • example-app follows fizzy main on its own: a workflow that repins it when fizzy releases.
  • #312: fizzy's backend as a package of its own (#243's "On fizzy's side"): SDLBackend, GpuRenderer, platform/**, viewport_map, the SDL pin.
  • Popout's generic half moves into it: subwindows, dialogs and menus into OS windows, driven by dvui's drawRetained and screensSet (#278).
    • #324: the viewports API is the package's, with a stand-in (viewports_none) for backends without OS windows; #328 makes -Dnative-backend=sdl3 build again.
    • #326: one way to draw a viewport's picture, viewports.Picture (stacked on #324).
    • #329: fizzy.addDvui, a dvui app of its own on fizzy's backend or dvui's (stacked on #326).
    • #330: a demo's pointer shows over float, menu and dialog windows (stacked on #326).
  • #325: fizzy adopts dvui.screensSet in place of core.screens' dvui-data plumbing.
  • example-app's run-dvui: a plain dvui app on that backend. Its floating windows are OS windows (fizzyedit/example-app#4, draft until #329 lands); menus and dialogs later, once the app can say which subwindows are menus.
  • The two dvui changes proposed upstream (foxnne/dvui-dev branches window-draw-retained, screens-set), with run-dvui as the demonstration.
Lingua principale
Zig
Stelle
1.5k
Fork
40
Merge medio
5h 35m
PR unite (30g)
151

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

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 fizzyedit/fizzy

Tutte le issue di fizzyedit/fizzy

Issue simili

Altre issue su Build System

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.