How haruma-k/addler works
Core Components
• Lifetime Binding System
• Preloading System
• Object Pooling System
• Addler |
• Lifetime Binding | | Preloading | | Object Pooling | |
Component Details
a. Lifetime Binding System:
• IReleaseEvent interface
• To implementations (MonoBehaviourBasedReleaseEvent, ParticleSystemBasedReleaseEvent)
• Binding relationship with Unity GameObjects
b. Preloading System:
• AddressablePreloader class
• Connection to Unity's Addressable system
• Preload and synchronous retrieval flow
c. Object Pooling System:
• AddressablePool class
• Pool management flow
• Instance lifecycle
Specific relationships
• GameObject -----> IReleaseEvent <----- LifetimeBinding
• AddressablePreloader -----> Addressables
• AddressablePool -----> Addressables
Important notes
• UniTask integration as optional
• Compile-time switches (ADDLER_DISABLE_PRELOADING, ADDLER_DISABLE_POOLING)
• Async/sync operations
Optional features and integration points
• Core Systems: Blue
• Unity Integration: Green
• External Dependencies: Orange
• Optional Features: Gray
• Special symbols (if any)
• Optional feature indicators
This will provide a clear visualization of how Addler manages memory and integrates with Unity's systems while maintaining proper separation of concerns and showing the relationships between components.
Remember to show both compile-time and runtime relationships, and indicate where async operations occur versus sync operations. This is particularly important for the preloading system's behavior.