How anshrjpt/dev-log works
DevLog is a C++ command-line developer journal. Its main workflow is to collect a daily session, save it in the logs, and use saved entries for summaries or a generated HTML report. The README documents the command set and report contents; the sampled source confirms entry display and some log-reading behavior, but the excerpt omits much of the command router and report implementation.
Main entry points: main.cpp Command router · 2026-03-02.txt Entry logs · report.html HTML report
Components 11
CLI and journal
- Command router
main.cpp - Daily entry
main.cpp - Entry logs
logs/2026-03-02.txt - Browse entries
main.cpp - Edit entry
main.cpp - Search entries
main.cpp
Journal insights
- Stats dashboard
main.cpp - Weekly summary
main.cpp
HTML reporting
- Report generator
main.cpp - HTML report
reports/report.html
Other components
- Developer
Connections 16
- Developer → Command router: runs command
README.md - Command router → Daily entry: dispatches new
README.md - Daily entry → Entry logs: saves entry
README.md - Command router → Browse entries: dispatches list/read
README.md - Browse entries → Entry logs: reads entries
main.cpp - Command router → Search entries: dispatches search
README.md - Search entries → Entry logs: searches entries
README.md - Command router → Edit entry: dispatches edit
README.md - Edit entry → Entry logs: updates entry
README.md - Command router → Stats dashboard: dispatches stats
README.md - Stats dashboard → Entry logs: reads entries
README.md - Command router → Weekly summary: dispatches week
README.md - Weekly summary → Entry logs: summarizes entries
README.md - Command router → Report generator: dispatches report
README.md - Report generator → Entry logs: reads logs
README.md - Report generator → HTML report: generates HTML
README.md