Backlog Editor — Phase B–D (Oct 2026)
Phase A (materials save, asset previews, ImGui IDs) landed in the same sprint. This document tracks items 4–7 from the product list.
4. Image Manager tab#
Goal: Preview, manipulate, and edit 2D images, textures, and related assets.
Proposed slices:
- Docked panel
ImageManagerPanel— open from View/Modules; list recent + project textures. - Canvas: zoom/pan, channel view (RGBA), sRGB toggle, metadata (resolution, format).
- Non-destructive ops first: resize, flip, generate mips preview; export to
.png/recompile to.cafviaTextureCompiler. - Optional: simple paint/rect fill (can delegate heavy work to Convoy Architect long term).
Touch points: AssetBrowser (open image here), TextureCompiler , EditorContext , layout profiles in settings.
5. Animation core + tab + animator#
Goal: 2D and 3D animation with state-machine style transitions; scriptable from Lua and C++.
Proposed slices:
- Core (
src/caffeine/animation):AnimationClip(keyframes: transform, sprite frame, morph),AnimationPlayercomponent, clock/evaluator shared by 2D/3D. - Editor tab: timeline already stubbed (
animationTimeline,animatorController) — Wire to core assets (.anim,.controller). - Animator: graph nodes (states, transitions, conditions: float/bool/trigger), blend trees for 3D.
- API: C++ public headers in
caffeine-core; Lua bindings mirroringAnimationPlayer+AnimatorControllersetters.
Dependencies: scene serialization, existing skeletal/mesh path for 3D; sprite/tile components for 2D.
6. Post-processing plugin (complete)#
Goal: Use HDR forward + PostProcessStack end-to-end in editor and runtime.
Proposed slices:
- Audit
PostProcessEditorUIvs runtime stack — ensure same effect order and parameter IDs. - Register plugin with editor menu; persist stack per scene or global volume component.
- Viewport + gameplay preview both route through stack when enabled.
- Document effect list and Lua/C++ hooks for toggling volumes.
- Touch points:* recent commit “HDR forward PBR pipeline, GPU post stack”;
doppio-plugins/if packaged separately.
7. Pathfinding base + AI development plugin#
Goal: Engine-level nav/path API; editor plugin to author NPC behaviour (not combat-only).
Proposed slices:
- Core: nav mesh or grid abstraction (
NavMesh,PathQuery), async request queue, debug draw in viewport. - ECS:
NavAgent+AIControllercomponents; steering along path. - Plugin: behaviour trees or state scripts (Lua), templates for patrol/chase/interact; visual debugger.
- Integration: use physics/world queries from existing Bullet integration where applicable.
Suggested PR order#
- Image Manager (vertical slice, user-visible).
- Animation core + minimal clip playback in viewport.
- Post-process plugin completion (smaller, builds on recent pipeline work).
- Pathfinding + AI plugin (largest; split core vs plugin).