How u-c-s/hurl works
Main Components Identification
The system consists of three main .NET applications and a browser extension:
• Browser Selector (Main UI Application)
• Settings Application
• Launcher (Rust-based)
• Browser Extension (Chrome)
Key Architectural Elements
a. Core Components:
• Library Layer (Hurl.Library)
• Contains shared models and core functionality
• Handles browser detection and rule matching
• Manages settings and JSON operations
b. User Interface Components:
• Browser Selector (Hurl.BrowserSelector)
• Main window for browser selection
• Time selection window
• URI handling and launching
c. Settings Management (Hurl.Settings)
• Configuration interface
• Rule management
• Browser management
d. Integration Components:
• Launcher (Rust-based entry point)
• Chrome Extension
• Windows Protocol Handler Integration
[User Interaction Layer]
• ↓
[Windows Protocol Handler]
• ↓
[Rust Launcher]
• ↓
[Core Applications]
• → [Browser Selector]
• → [UI Components]
• → [URI Handler]
• → [Settings App]
• → [Rule Management]
• → [Browser Config]
• → [Hurl Library]
• → [Models]
• → [Rule Matching]
• → [Browser Detection]
[Browser Extension] ←→ [Browser Selector]
Important Details
a. Data Flow:
• How URLs are processed from click to browser launch
• Settings and rule synchronization
• Browser detection and selection flow
b. Integration Points:
• Windows protocol handler registration
• Browser extension communication
• File system interaction for settings
c. Key Technologies:
• .NET 8 Desktop Runtime
• Windows App SDK
• Rust (for launcher)
• Chrome Extension API