How ikebastuz/wiper works
Main Components
a) Core Components:
• File System Scanner (src/fs)
• User Interface Layer (src/ui)
• Event Handler System (src/events)
• Task Manager (src/task_manager)
• Configuration Manager (src/config)
b) Supporting Components:
• Logger System (src/logger)
• FPS Counter (src/fps_counter)
• Spinner Animation (src/spinner)
Component Relationships
┌─ User Interface Layer ─────────────────────┐
• Chart Display │
• Content View │
• Footer Controls │
• Title Bar │
• ┬───────────────────────┬─┘
┌─────────────────▼───────────────────┐ │
• Event Handler │ │
• User Input Processing │ │
• Command Routing │ │
• ┬───────────────────┘ │
┌─────────────────▼───────────────────┐ │
• Task Manager │ │
• File Operations │ │
• Directory Navigation ◄├───┘
• ┬───────────────────┘
┌─────────────────▼───────────────────┐
• File System Layer │
• Directory Scanner │
• File Store (HashMap) │
• Folder Entry Management │
• ┬─┘
• ▲ │
┌─────────────────┴─────────────────▼─┐
• Operating System File System │
• ┬─┘
Important Details
a) Component Responsibilities:
• UI Layer: Handles user interface rendering and updates
• Event Handler: Processes user inputs (keybindings)
• Task Manager: Manages file operations and navigation
• File System Layer: Handles file scanning and storage
b) Cross-cutting Concerns:
• Logger: System-wide logging
• Configuration: Global settings management
• FPS Counter: Performance monitoring
• Spinner: Loading state indication
Technical Details
• Rust-specific implementations
• Integration with system file operations
• Cross-platform compatibility points
• Performance-critical paths