How awolven/krma works
Main Components
a) Application Layer
• Application interface (application-mixin.lisp)
• Scene management (scene-mixin.lisp)
• Demonstrate CLUI support integration (clui-support.lisp)
b) Graphics Pipeline
• Vulkan Backend (vulkan-pipelines.lisp)
• Shader Components (*.vert and *.frag files)
• Pipeline Combinations (pipeline-combinations.lisp)
c) Rendering Systems
• Materials System (materials.lisp)
• Lighting System (lights.lisp)
• Text Rendering (text.lisp)
d) Resource Management
• Foreign Arrays Handler (foreign-arrays.lisp)
• Texture Management (implied by texture.frag)
• Groups System (groups.lisp)
[Application Layer]
• ↓
[Scene Management]
• ↓
[Graphics Pipeline]
• ↓
[Rendering Systems]
• ↓
[Resource Management]
• ↓
[Vulkan Backend]
Key Relationships to Highlight
• Bidirectional flow between Scene Management and Graphics Pipeline
• Demonstrate the relationship between shaders and the pipeline system
• Platform-specific backends (MacOS/Cocoa, Windows/Win32, Linux/X11)
Specific Elements
• Immediate Mode vs. Retained Mode rendering paths
• Platform abstraction layer
• Shader management system
• Memory management for graphics resources
• Text rendering pipeline with MSDF support
• External dependencies (show key submodules like cl-vulkan, 3d-math)
Data Flow Indicators
• How rendering commands flow from application to GPU
• Resource loading paths
• Demonstrate memory management flow
• How different rendering modes interact
Technical Details to Emphasize
• Vulkan integration points
• Platform-specific windowing system interfaces
• Memory management strategies
• Shader compilation and management
• Pipeline state management
• Component groupings
• Platform-specific elements
This will create a comprehensive visualization of KRMA's architecture while maintaining clarity and usefulness for technical discussions and system understanding.