Domain: Creative Software Engineering, Open Source (FLOSS) Development, and Computational Graphic Design.
Expert Persona: Senior Software Architect and Technical Lead in Creative Technologies.
Abstract
This transcript captures two distinct presentations from the 2026 Libre Graphics Meeting (LGM). The first, "Freeze+Press" by Christoph, explores a "software-driven small press" that utilizes Free/Libre Open Source Software (FLOSS) to bridge experimental graphic design with physical production. Christoph details a workflow where bash scripts and modular illustrations generate generative art, disseminated through a mail-order model that emphasizes sharing source repositories over finalized assets.
The second presentation, by Jules, is a technical post-mortem and evaluation of modern UI frameworks for the "Cool Lab" project. Jules outlines the architectural challenges of migrating from C++ and Dear ImGui to a more robust layout system. The analysis compares Electron, Tauri, and Dioxus, ultimately concluding that "immediate mode" UIs (specifically the Rust-based Egui) remain superior for real-time creative tools due to their lack of complex state synchronization ("signals") and reduced overhead in handling high-frequency data like GPU textures.
Summary of Presentations
Part 1: Freeze+Press (Christoph)
0:00:33 — Project Definition: Introduction of "Freeze and Press," a FLOSS-driven small press. The name reflects a convergence of physical phase shifts, breakdancing aesthetics, and software unresponsiveness.
0:02:01 — DIY Lineage: Christoph traces the project’s roots to 1999 DIY culture, citing early frustrations with proprietary "locked" environments like Macromedia Flash and Microsoft FrontPage as catalysts for moving to open-source alternatives.
0:05:32 — Academic and Cultural Context: The speaker credits the Kunsthochschule für Medien (KHM) in Cologne for introducing him to the "culture and cult" of Unix and GNU/Linux.
0:07:21 — Bash as a Design Tool: For the 2008 Linux Audio Conference, Christoph utilized bash scripts and modular illustrations to generate generative posters, establishing a "design rules to design graphics" philosophy.
0:09:12 — The Research Lab/Bookshop Hybrid: The project operates as a research lab disguised as a mail-order shop. It prioritizes the sale of physical "electricity-free" objects while providing light-speed access to digital source code.
0:11:45 — Source Code Transparency: Unlike traditional tutorials, the project links directly to live Git source trees (active since 2013), favoring the "daily mess" of a working environment over sterilized galleries.
0:16:18 — Media Ecology/Stickers: The press produces merchandise based on historical software artifacts, such as the Netscape Navigator "Broken Image" icon and the Ghostscript "Canonical Tiger" test image.
Part 2: Exploring Modern UI Frameworks (Jules)
0:26:06 — The Layout Problem: Identification of Dear ImGui’s primary weakness: the inability to handle complex layouts (e.g., automatic wrapping, right alignment, and grid spacing) without manual pixel-coordinate calculations.
0:28:25 — Evaluating Layout Engines (Clay): Brief experimentation with Clay, a standalone layout engine. It was rejected due to its immaturity and lack of essential features like overflow wrapping.
0:30:51 — Web Technologies Pros/Cons: Discussion of Electron and web stacks. Key advantages include "Hot Reloading" and massive ecosystem support; however, the C++ to JavaScript bridge creates debugging and architectural friction.
0:35:16 — The Transition to Rust: Decision to rewrite the "Cool Lab" back end in Rust to utilize modern memory safety and performance.
Tauri: High overhead in synchronizing state between the Rust back end and JavaScript front end.
Dioxus: Solves language fragmentation by using Rust for both front and back ends but still requires "signals" for state tracking.
0:39:48 — Texture and Latency Challenges: Web-based frameworks (CEF/Electron) struggle with real-time GPU texture sharing, often requiring high-latency CPU-side copying to display rendered frames in the UI.
0:44:43 — Immediate Mode vs. Retained Mode: The speaker distinguishes between "Retained Mode" (Web/Dioxus), which requires state tracking and callbacks, and "Immediate Mode" (Dear ImGui/Egui), which re-renders every frame based on the current engine state.
0:46:28 — Final Choice (Egui): Selection of Egui (a Rust immediate-mode library) as the optimal solution. It maintains the simplicity of Dear ImGui while providing superior layout capabilities like automatic element wrapping.
0:50:42 — Framework Comparisons: During Q&A, the speaker addresses Qt, GTK, and JUCE, characterizing them as possessing "accidental complexity" compared to the streamlined nature of modern Rust-based immediate-mode UIs.
Key Reviewers for This Topic
Creative Technologists: To evaluate the intersection of generative art and open-source tools.
UI/UX Engineers (Systems Level): To review the technical trade-offs between immediate and retained mode architectures.
FLOSS Community Members: To discuss the ethics of source-code transparency and experimental publishing.
Rust/C++ Developers: To analyze the performance implications of the proposed UI migrations.