What problem does it solve?
When a new Gum runtime feature ships, developers need a visual demo screen to eyeball it across backends, but keeping the MonoGame, raylib, and Silk.NET feature samples aligned is error-prone — screens drift out of order, texture paths differ, and backend-specific properties break compilation.
Core Features & Use Cases
- Cross-backend screen mirroring: Add a new feature screen to MonoGameGumInCode, the raylib gallery, and SilkNetGum with matching section order so side-by-side visual comparison exposes backend rendering bugs.
- Backend gotcha guidance: Handles differing texture paths, color types (XNA Color, Raylib_cs.Color, SKColor), #if-gated properties, and linked screen files via csproj Compile Include entries.
- Shape demo setup: Covers Circle, Rectangle, Arc, Polygon demos including the MonoGame Gum.Shapes package requirement, ShapeRenderer.Self.Initialize, and HiDef graphics profile.
- Use Case: After fixing a raylib-only render-target bug, add the demo cell to all three mirrored screens at the same relative position so reviewers can compare rendering across backends.
Quick Start
Add a demo screen for the new NineSlice feature to the MonoGame, raylib, and SilkNetGum feature samples, keeping all three mirrored section-for-section.