How 9front/drawterm works
Main Components Identification
The system should be represented with these primary components:
a) Core Components:
• Authentication System (libauth, libauthsrv)
• Kernel Emulation Layer (kern/)
• GUI Implementations (multiple gui-* directories)
• Security Services (libsec)
• Drawing Systems (libdraw, libmemdraw)
b) Platform-Specific Components:
• Android Implementation
• Windows Implementation
• Unix/Linux Implementation
• macOS Implementation (Cocoa and X11)
┌─ User Interface Layer ─────────────────────┐
• GUI Implementations: │
• Cocoa (gui-cocoa) │
• X11 (gui-x11) │
• Android (gui-android) │
• Windows (gui-win32) │
• ┬───────────────────────┘
• ↓
┌─ Core Services Layer ──────────────────────┐
• ┌─────────────┐ ┌──────────┐ ┌──────────┐ │
• Authentication│ │ Drawing │ │ Security │ │
• Services │ │ System │ │ Services │ │
• ┘ └──────────┘ └──────────┘ │
• ┬───────────────────────┘
• ↓
┌─ Kernel Emulation Layer ──────────────────┐
• Device Emulation │
• Process Management │
• File System Interface │
• ┬───────────────────────┘
• ↓
┌─ Platform Abstraction Layer ──────────────┐
• POSIX Implementation │
• Windows Implementation │
• ┬───────────────────────┘
• ↓
┌─ Host System Layer ────────────────────────┐
• Operating System (Android/Unix/Windows/Mac)│
• ┘
Important Details
• Authentication flows (DP9IK authentication support)
• TLS-based rcpu protocol connections
• Device emulation paths (devfs, devip, devaudio)
• Platform-specific GUI implementations
• Security service integrations
Component Relationships
Following key interactions:
• GUI layers → Drawing System
• Authentication Services → Security Services
• Kernel Emulation → Platform Abstraction
• Device Emulation → Host System Services
Implementation Notes
• A note about Android-specific limitations (plaintext login storage)
• Build configuration paths
• Platform-specific compilation requirements