How azurice/ranim works
Main Components
a. Core Engine Components:
• Scene Management System
• Animation Pipeline
• Rendering System
• Object Management System
b. External Dependencies:
• WGPU (Graphics API)
• FFmpeg (Video Encoding)
Application Layer
Scene Management Layer
Object/Animation Layer
Rendering Layer
Output Layer
Key Components and Relationships
a. Scene Management Layer:
• Scene Store (src/scene/store.rs)
• Entity Management (src/scene/entity.rs)
• Canvas System (src/scene/canvas/)
• File Writer (src/scene/file_writer.rs)
b. Object/Animation Layer:
• RObject System (src/rabject/)
• 2D Objects (rabject2d/)
• 3D Objects (rabject3d/)
• Animation System (src/animation/)
• Transform Animations
• Fading Animations
c. Rendering Layer:
• WGPU Integration (src/utils/wgpu.rs)
• Shader Pipeline
• Multiple shader files for different purposes (fill, stroke, compute)
• Canvas Pipeline (src/scene/canvas/pipeline.rs)
Specific Design Elements
• Rectangles: Core components
• Hexagons: External dependencies
Important Relationships to Highlight
• Scene → Objects: Composition relationship
• Objects → Shaders: Rendering pipeline
• Animation System → Objects: Transformation flow
• Canvas → WGPU: Graphics rendering
• File Writer → FFmpeg: Video encoding
Technical Details
• Shader Pipeline Architecture
• Compute shaders
• Fill/Stroke operations
• Object Hierarchy
• 2D/3D separation
• Vector paths
• Mesh objects
Implementation Notes
• The separation between 2D and 3D rendering pipelines
• The relationship between animations and objects
• The shader pipeline architecture
• The video encoding process