How vihdzp/miratope-rs works
Main Components
The system should be divided into these key components:
a) Core Engine (miratope-core):
• Abstract Polytope System (abs/)
• Concrete Polytope System (conc/)
• Coxeter Groups Handler (cox/)
• File Operations (file/)
• Geometry Engine
• Theory Implementation (group/)
b) Frontend/UI Layer:
• Main Window System
• Camera Controls
• Configuration Management
• Library Browser
• Right Panel Interface
• Top Panel Interface
• Wiki Integration
c) Rendering Pipeline:
• No-Cull Pipeline
• Mesh System
• Shader Management (GLSL)
d) Resource Management:
• Polytope Library (.off files)
• Memory Management
[User Interface Layer]
• ↕
[Rendering Layer]
• ↕
[Core Engine Layer]
• ↕
[Resource Layer]
Component Relationships
Key interactions:
• UI → Rendering Pipeline: Display requests
• UI → Core Engine: Polytope operations
• Core Engine → Resource Layer: Library access
• Rendering Pipeline → Core Engine: Geometry data
• Core Engine ↔ File System: Import/export operations
Implementation Details
Technical aspects:
• Rust as primary language
• WGPU for graphics
• Custom shader implementation
• File format parsers
• Mathematical operations
External Dependencies
Connections to:
• Rust ecosystem
• Graphics libraries
• Math libraries
• File system
This architecture reflects both the mathematical complexity of polytope operations and the need for efficient visualization, while maintaining a modular structure that allows for future extensions and modifications.