Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

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

オープン
  • 何か問題がありますか？
#281 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
12/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
zig
領域
build-system, ci-cd, desktop-dev

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.
主要言語
Zig
スター
1.5k
フォーク
40
平均マージ
5時間 35分
マージ済み PR（30日）
151

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

fizzyedit/fizzy のほかの issue

fizzyedit/fizzy の issue をすべて見る

似ている issue

Build System の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。