How scellecs/morpeh works
High-Level Architecture (Main Layer)
• Entities | --> | Components | --> | Systems |
• (Identifiers) | | (Data) | | (Logic) |
• ↓ ↓ ↓
• World (Container) ---------------+
Core Components Layer (Second Layer)
• Filter | | Stash | | SystemsGroup |
• (Query Logic) | |(Data Storage)| |(System Mgmt.) |
• ↑ ↑ ↑
• World |
Implementation Details Layer (Third Layer)
Create sections for specific implementations:
• Native Support | --> | Unity Integration|
• (Jobs & Burst) | |(MonoProviders) |
• ↓ ↓
• Collections | --> | Plugins |
• (Custom DS Impl.) | |(Extensions) |
Key Features to Highlight
• Archetype-Based Design |
• Separate Data Store |
• Filter Optimization |
• Cache-Friendly |
• Safety Features |
• Thread Safety |
• Component Disposal |
• Debug Tools |
Additional Elements
• World Browser tool
• Benchmarking components
• Testing infrastructure
• Unity Editor integration
Debug and development tools
Remember to include notes about:
• Thread safety considerations
• Performance optimization features
• Unity-specific integration points
• Plugin system architecture
• Debug and development tools
This will provide a complete picture of the framework's architecture while maintaining clarity and readability.