How jwezel/term works
Core Library Components (Main Layer)
• Term Module (/src/term)
• Subcomponents for:
• Management (display.hh)
• Window Management (window.hh)
• Event Handling (event.hh)
• Geometry Processing (geometry.hh)
• Surface Rendering (surface.hh)
UI Layer (/src/ui)
• Components for:
• Container Management
• Element Handling
• Frame System
• Widget System
• Window Management
Utility Layer (/src/util)
• Utilities for:
• Error Handling
• String Processing
• Hash Functions (xxh32/64)
External Dependencies
• Connections to:
• Boost
• Taitank (Flex-based layout engine)
• utfcpp
Use a layered architecture approach
[External Dependencies Layer]
• ↑
[UI Layer (src/ui)]
• ↑
[Term Core Layer (src/term)]
• ↑
[Utility Layer (src/util)]
Connection Types
Specific Implementation Details:
Term Core Layer
• Interaction between display, window, and surface components
• Event system's connection to keyboard and window events
• Demonstrate how geometry processing feeds into the surface rendering
UI Layer
• Hierarchy: Container → Elements → Widgets
• How frames and windows are managed
• Demonstrate the connection to the Taitank layout engine
Testing Framework
• A separate testing component showing connections to each major module
• Reference the test directory structure in /test
Key Architectural Patterns to Highlight:
Platform-specific components (ANSI terminal support)
Level of Detail:
• Keep high-level architectural components visible
• Abstract implementation details but show major class relationships
• Interfaces and communication paths
• External dependency integration points
Remember to emphasize:
• The separation between terminal operations and UI components
• The flexibility of the output device mechanism
• The layout engine's role in the system
• Event handling and propagation paths