How gothenburgbitfactory/taskwarrior works
Main Components
a. Core Components:
• Task Management Engine (src/Task.cpp, src/TDB2.cpp)
• Command Line Interface (src/CLI2.cpp)
• Data Object Model (src/DOM.cpp)
• Configuration System (src/Context.cpp)
• Hook System (src/Hooks.cpp)
b. Supporting Systems:
• Database Layer (TDB2)
• Filter System (src/Filter.cpp)
• Command Processing System (src/commands/*)
• Column Display System (src/columns/*)
• Sync Infrastructure (src/commands/CmdSync.cpp)
Architectural Relationships
CLI Layer → Command Processing → Task Management Engine → Database Layer
• ↓
• Hook System
• ↓
• External Scripts/Add-ons
Key Design Elements
• Blue: Core components (Task Engine, DOM)
• Green: Interface components (CLI, Commands)
• Yellow: Data storage components (TDB2)
• Orange: Extension points (Hooks)
• Purple: External integrations
b. Component Types:
• Use rectangles for core modules
• Use hexagons for interface points
Detailed Component Breakdown
a. Task Management Core:
Task Engine
• Task Object Model
• Recurrence Engine
• Dependency Manager
• Urgency Calculator
b. Interface Layer:
CLI
• Command Parser
• Filter Processor
• Output Formatter
c. Storage Layer:
TDB2
• Data Storage
• GC Management
• Sync Protocol
Integration Points
External integration capabilities:
• Hook System connections
• Sync protocol interfaces
• -on script integration
• Theme system
• UDA (User Defined Attributes)
Implementation Notes
• Maintain consistent spacing and alignment
• Related components visually
• Use clear, readable labels
• Version information
This architecture reflects a well-structured command-line application with clear separation of concerns between UI, business logic, and data storage, while maintaining extensibility through a robust hook system.