gfx: no image blit, no additive blend, no polygon/gradient, no font API — the 15-primitive surface caps every consumer at a 1982 look (Tidepool forcing-function)
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
- 35/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- c
- Área
- computer-graphics, testing-qa
Línea de trabajo
Start in src/ext_gfx.c, focusing on the existing SDL loader, framebuffer texture path, and current gfx primitives. Review src/draw.eigs and the lib/ui consumers, then inspect how headless draw-list entries and gfx_read pixel tests are structured under xvfb. Done means the requested image, blend, geometry, alpha, and font capabilities are implemented with dependency-free loading and coverage for each builtin.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Forcing-function report from Tidepool (maintainer's call, 2026-09-20: the gfx fleet "looks like it was from the early 80s — necessary to have started there, for the language, but not modern"). Measured against src/ext_gfx.c on main a22f8dd, the runtime's drawing surface is 15 builtins: gfx_open close title clear present poll delay ticks clip read fb point line rect rrect circle text text_width text_height. What a modern-looking 2D game needs and cannot get from that set:
Already there (so the ask is smaller than it looks): a global SDL_BLENDMODE_BLEND (line 486); gfx_rect/gfx_circle take an optional alpha (538–612); textures exist internally (SDL_CreateTexture/UpdateTexture/RenderCopy are loaded for gfx_fb); SDL2_ttf is probed for gfx_text; inflate/deflate builtins exist (make zlib).
Missing:
- No image path. Nothing loads a raster or blits one. Every consumer draws with circles and lines; a background plate, a sprite, a particle texture, a generated concept art (Tidepool docs/concept-2026-09-20.png, made in one minute) cannot reach the screen. Ask:
gfx_image_load of path→ handle (PNG decode in C on top of the existing inflate — no SDL2_image dependency, which is not on the dev box anyway; RGBA with real alpha),gfx_image_draw of [img, x, y, w, h, alpha, angle_deg],gfx_image_size, and a framebuffer-backedgfx_image_from_fbso procedural art can be cached once and blitted many times. - No additive blend. Glow is
BLENDMODE_ADD; a bioluminescent look is impossible with alpha-blend only. Ask:gfx_blend of mode("blend" | "add" | "none"), state held per subsequent draw. gfx_line/gfx_pointhave no alpha (rect/circle do). Ask: same optional trailing alpha on all four.- No filled polygon / gradient / soft circle. A cell body is a smooth blob, a water background is a gradient, a glow is a radial falloff. Ask:
gfx_polygon of [[x,y]…, r, g, b, a](SDL_RenderGeometry, already in SDL2 ≥ 2.0.18) andgfx_circle_soft of [cx, cy, radius, r, g, b, a, feather]— or justgfx_polygonplus item 1 and letlib/build the rest. - Text is a bitmap font unless a system TTF happens to be found, with no size/weight API beyond scale. Ask:
gfx_font of [path, size]→ handle,gfx_textaccepting a font handle.
Consumer evidence: Tidepool's renderer uses exactly gfx_circle/line/rect/rrect/point/text/clear/present (src/draw.eigs), DMG uses gfx_fb, DeslanStudio uses lib/ui on the same primitives. All three are capped by the same five gaps. The identity of the Tidepool look (translucent, glowing, dark pool) survives — it needs items 1, 2 and 4 to render the way the concept frame shows it.
Keep it dependency-free (EigenScript has none): PNG via inflate, geometry via SDL_RenderGeometry through the existing dlsym loader, nothing new to link. Each builtin lands with a headless draw-list entry (the renderer is headless-inspectable and consumers' tests assert on it) and a gfx_read pixel test under xvfb.
- Lenguaje dominante
- C
- Estrellas
- 3
- Forks
- 7
- Merge medio
- 3 h 58 min
- PR fusionados (30 d)
- 105
Preparar el entorno
Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.
- Incluye un Dockerfile o un archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de InauguralSystems/EigenScript
-
area:lint-tooling bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
InauguralSystems/EigenScript#1340 ·
Los mantenedores suelen responder en 1 día
-
area:stdlib found-by:code-review kind:silent-wrong
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
InauguralSystems/EigenScript#1338 ·
Los mantenedores suelen responder en 1 día
-
area:lint-tooling found-by:critic kind:docs-drift
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
InauguralSystems/EigenScript#1335 ·
Los mantenedores suelen responder en 1 día
-
area:ci found-by:critic kind:gate-defect
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
InauguralSystems/EigenScript#1311 ·
Los mantenedores suelen responder en 1 día
-
enrolment: decide test_gc_runner_controls.py (exempt vs enrol) and whether floors need a ratchetAbiertoarea:gates found-by:critic kind:decision
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
InauguralSystems/EigenScript#1280 · 1 comentario ·
Los mantenedores suelen responder en 1 día
Todos los issues de InauguralSystems/EigenScript
Issues similares
-
Dificultad 1/5 1-3 horas Aptitud para principiantes 88/100
ClickHouse/pg_clickhouse#383 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
johnsonjh/emu2-cpm86#68 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Zenmap CrashAbiertoZenmap
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Los mantenedores suelen responder en 2 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
BasedHardware/omi#19306 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
fastfetch-cli/fastfetch#2619 ·
Los mantenedores suelen responder en 1 día