How wowserhq/client works
Key Components to Include:
Core Application Layer
• Entry point (Client.ts)
• Main application lifecycle management
• Connection between major subsystems
Graphics Engine (src/gfx/)
• Multiple Graphics APIs Support
• WebGL2 Implementation
• WebGPU Implementation
• Device Management
• Shader System
• Texture Management
• Screen/Layer Management
UI System (src/ui/)
• Component Hierarchy
• Template System
• Rendering Pipeline
• Event System
• Scripting Engine
Resource Management
• Asset Loading
• Shader Management
• Texture Registry
• Template Registry
Use a layered architecture approach
• Top Layer: Client Interface
• Middle Layer: Core Systems
• Bottom Layer: Graphics APIs
Component Relationships
• Clear hierarchical relationships between UI components
• Data flow between graphics pipeline stages
• Demonstrate resource loading paths
Specific Elements to Include:
Graphics Pipeline
WebGL2/WebGPU API → Device → Shader Registry → Texture Registry → Screen Renderer
UI Component System
UIRoot → Layout Frames → Simple Components
• ↓
Script Engine → Event System
Resource Loading Flow
Asset Loader → Template Registry → Component Factory → Live UI
Important Considerations:
Separation between
• Graphics rendering system (WebGL2/WebGPU)
• UI component system
• Scripting/event system
Clear boundaries between
• Core engine code
• WoW-specific implementations
• Browser APIs
Special attention to
• Shader management (public/Shaders/)
• UI template system (XML-based)
• Lua scripting integration
Performance-Critical Paths
• Render batch processing
• Event handling
• Resource loading
Notes for important implementation details
Key Technical Details to Highlight: