How fawn-edu/cs2450-todo works
Task Manager is a desktop todo-list application. At startup, main reads todo.txt and parses its task records, then constructs the controller and runs the FLTK interface. Users can view all, incomplete, or completed tasks and create, edit, complete/reopen, or delete them; UI actions are represented by commands that update the controller’s in-memory task list. On exit, main writes the tasks back to todo.txt. The README offers little architectural detail, so this map follows the sampled implementation and does not infer unsampled features.
Main entry points: main.cpp Application entry · task_view.cpp Task view · task_controller.cpp Task controller · task_command.hpp Task commands
Components 7
Application and storage
- Application entry
src/main.cpp - todo.txt
Desktop interface
- Task view
src/task_view.cpp - Task commands
src/task_command.hpp
Task domain
- Task controller
src/task_controller.cpp - Task model
src/task.cpp
Other components
- User
Connections 10
- User → Task view: uses
src/task_view.cpp - Application entry → todo.txt: reads
src/main.cpp - Application entry → Task model: parses
src/main.cpp - Application entry → Task controller: constructs
src/main.cpp - Application entry → Task view: runs
src/main.cpp - Task view → Task controller: queries
src/task_view.cpp - Task view → Task commands: dispatches
src/task_view.cpp - Task commands → Task controller: executes on
src/task_command.hpp - Task controller → Task model: mutates
src/task_controller.cpp - Application entry → todo.txt: writes
src/main.cpp