How vagabond-k/vegraris works
Core Architecture Components
• Vegraris.Core (Game Logic Layer)
• Vegraris.Wpf (WPF Client)
• Vegraris.Wasm (Blazor WASM Client)
Detailed Component Breakdown
a) Core Layer (Vegraris.Core):
• Game Logic (Game.cs, Grid.cs, GridEditor.cs)
• Piece Management (Piece.cs, ActivePiece.cs, LockedPiece.cs, StaticPiece.cs)
• Drawing System (Drawing/ folder)
• Palette System (Palettes/ folder)
• Tracing System (Tracing/ folder)
• Input Management (PlayerInputDispatcher.cs)
• Scoring System (IScoring.cs, DefaultScoring.cs)
b) Client Implementations:
WPF Client (Vegraris.Wpf):
• MVVM Architecture components
• Theme System (Themes/ folder)
• Converters
• Sound System
• WPF-specific Drawing Implementation
Blazor Client (Vegraris.Wasm):
• Razor Components
• JavaScript Interop
• WASM-specific Drawing Implementation
• State Management
Interaction Flows
• Data flow between Core and Clients
• Event propagation
• Drawing instruction flow
• Input handling flow
Platform-Specific Implementations
• The separation between core game logic and platform-specific implementations
• The vector graphics drawing system's architecture
• How themes are implemented across platforms
• The event system for game state changes
• Platform-specific optimizations
Remember to:
• Keep the core game logic (Vegraris.Core) completely platform-independent
• How the drawing system abstracts vector graphics operations
• How different themes are implemented and switched
• Demonstrate the input handling flow from user interaction to game state changes
This architecture should clearly show how the project maintains platform independence while allowing for platform-specific optimizations in both WPF and Blazor WASM implementations.