How epsitec-sa/grafix works
Main Components
a. Core Layers:
• C# Binding Layer (AggUI)
• Native C++ Layer (aggcpp)
• External Dependencies (Antigrain Geometry, FreeType)
b. Platform-Specific Components:
• Windows Implementation
• macOS Implementation (with Xorg)
• Linux Implementation
[Application Layer]
• ↓
[C# Binding Layer]
• ↓
[Native C++ Layer]
• ↓
[Platform-Specific Layer]
Component Details
C# Binding Layer should show:
• AggWindow (Window management)
• GraphicContext (Drawing context)
• GraphicBuffer (Memory management)
• FontManager (Font handling)
• Rasterizer (Rendering pipeline)
• Renderer (Drawing operations)
Native C++ Layer should include:
• Antigrain Geometry integration
• FreeType integration
• Platform-specific window handling
Data Flow
Following interactions:
• Application → C# Bindings (method calls)
• C# Bindings → Native Layer (P/Invoke)
• Native Layer → External Libraries
• Native Layer → Platform-specific implementations
Component Relationships
• How GraphicContext orchestrates rendering operations
• How FontManager interfaces with FreeType
• How AggWindow interfaces with platform-specific window implementations
• How Rasterizer and Renderer work together
Implementation Details
Implementation patterns:
• P/Invoke boundary between C# and C++
• Platform abstraction layer
• Memory management strategy
• Event handling system