Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

embedding: fizzy's editor on a host's dvui backend (Blender, Unreal)

Abierto
  • ¿Algo no está bien?
#529 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
zig
Área
desktop, game-dev

Línea de trabajo

Start by reading src/fizzy.zig and the existing test-integration build, then trace Entry and the global fizzy.entry() and fizzy.editor() assumptions described in the issue. The requested work needs a plan for separating process setup from the editor and defining the embedded API, host services, and window chrome options. Done means a host can build and run the editor on its dvui window with host-provided config, dialogs, and quit behavior.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement

Feature request from Graphl, which runs inside Blender and Unreal through blender-dvui and unreal-dvui. Each host owns the process and drives a *dvui.Window through dvui's init/frame/deinit. Graphl keeps a second shell of about 1200 lines for those hosts, and would like to run fizzy's editor there instead.

What's in the way:

  1. The build. Native backends are a closed set, and there's no way to get fizzy's editor as a module on a host's dvui and backend. test-integration already builds src/fizzy.zig on dvui's testing backend, so most of the code is ready.
  2. Entry assumes it is the process. It does:
    • crash handlers and root panic/segfault decls
    • Velopack hooks
    • the single-instance lock
    • a chdir to the exe's folder
    • OS window state and chrome
  3. One editor per process. fizzy.entry() and fizzy.editor() are globals.
  4. Window chrome. The editor draws a title-bar strip, caption buttons and drag areas.
  5. Services the host should provide: file dialogs, config storage, what Quit does.

Shape suggested: split Entry into a process part (fizzy's executables only) and an editor part. Expose fizzy.Embedded.init(gpa, win, .{ .chrome = .none, .config, .dialogs, .on_quit }) with frame/deinit, built by fizzy.addEmbedded(dep, .{ .dvui, .backend, .plugins, ... }).

This is a large feature and needs a plan.

Plan update (2026-10-19)

The plan is rewritten around out-of-process embedding: the installed fizzy stays the one editor (started --quiet by the host's adapter when it is not running, exiting after a grace period when the last view closes) and a host such as Blender or Unreal shows a "remote view" of it over the control socket, rendered by one of three tiers (native surface, shared GPU texture, draw lists). Inside fizzy, its own windows and remote views share one ViewHost interface. The in-process Embedded design above is kept only as a fallback. See fizzyedit/plans#39 (plans/EMBEDDED_EDITOR_PLAN.md).

Lenguaje dominante
Zig
Estrellas
1.5k
Forks
40
Merge medio
4 h 39 min
PR fusionados (30 d)
428

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de fizzyedit/fizzy

Todos los issues de fizzyedit/fizzy

Issues similares

Más issues de Desktop Dev

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.