How attackgoat/screen-13 works
Main Components
a. Core Engine Layer:
• Driver Component (src/driver/*)
• Vulkan Instance Management
• Physical Device Management
• Command Buffer Handling
• Resource Management (buffers, images, etc.)
b. Render Graph System (src/graph/*)
• Graph Resolver
• Node Management
• Edge Management
• Resource Binding System
c. Resource Management Layer (src/pool/*)
• Resource Pooling
• Memory Management
• Resource Aliasing
d. Extension Components (contrib/*):
• Hot Reload System (screen-13-hot)
• UI Integration (screen-13-imgui, screen-13-egui)
• Effects System (screen-13-fx)
• Window Management (screen-13-window)
[Application Layer]
• ↓
[Window Management]
• ↓
[Render Graph System] ←→ [Resource Management]
• ↓
[Driver Layer] ←→ [Extensions]
• ↓
[Vulkan API]
Component Details
a. Driver Layer:
• Vulkan abstractions (Instance, Device, CommandBuffer)
• Smart pointer management
• Resource creation/management flow
b. Render Graph:
• Node/edge relationship
• Pipeline integration (Compute, Graphics, Ray-tracing)
• Demonstrate resource binding system
c. Resource Management:
• Pooling system
• Memory management flow
• Aliasing optimization
d. Extensions:
• How they plug into the core system
• Optional nature
• Integration points
Implementation Notes
• Use UML-style notation for clarity
• Brief descriptions for major components
• Version compatibility (Vulkan version support)
• Performance-critical paths
Key Relationships to Highlight
• Render Graph → Driver (resource utilization)
• Extensions → Core (integration points)
• Resource Management → Driver (memory optimization)
• Window System → Render Graph (frame presentation)