How nathancartlidge/powertoys-run-unicode works
Main Components
a. Input Layer:
• PowerToys Run Interface (entry point)
• Command Parser (for \ne, ×, etc.)
b. Core Processing Components:
• Lookup System
• AgdaLookup (for Latex-style inputs)
• HtmlLookup (for HTML entity inputs)
• BaseLookup (shared functionality)
• Character Mapping Storage (assets/mappings.txt)
c. Output Handlers:
• Typer (for direct input)
• Clipboard Manager (for clipboard operations)
Relationships and Data Flow
User Input -> PowerToys Run Interface -> Command Parser
• ↓
• ┌────────────── Lookup System ───────────┐
• ↓ ↓ ↓
• AgdaLookup BaseLookup HtmlLookup
• ↓ ↓ ↓
• Character Mapping ───────────┘
• ↓
• ┌─────────── Output Handler ────────────┐
• ↓ ↓
• Typer Clipboard Manager
Additional Details
• Testing Framework connection (showing test coverage)
• Configuration options (plugin.json settings)
• External dependencies (PowerToys Run API)
Implementation Notes
• Relationship between test files and their corresponding implementation
• Build/deployment workflow from GitHub Actions
• Separation between core functionality and extension points