How covesa/dlt-viewer works
Project type and purpose
• Desktop application (Qt-based GUI) + companion CLI tool
• Core function: import/parse DLT log streams (files, pcap, MF4), apply filters, view/export results, and send/receive control messages to a DLT daemon.
• Extensible via dynamically loaded plugins.
Main components
A. Presentation Layer
1. Qt GUI Application (“DLT Viewer”)
– Source in /src
– Classes: MainWindow, dialogs (filter, search, export, plugin), models/views (table model, proxy filter model), resource manager.
2. Command-line tool (“DLT Commander”)
– Source in /commander
– Parses CLI args, invokes core library to convert/filter logs without GUI.
B. Core Library (/qdlt)
• Parsing & decoding of DLT messages
• Filter engine & filter definition loader
• Plugin management (plugin interface, discovery, loading)
• Connection abstractions (file, stream, TCP/UDP, serial, D-Bus)
• Exporters/importers (text, CSV, DLT re-serialize)
C. Plugin Layer (/plugin)
• Each subfolder is a plugin implementing the qdlt::PluginInterface
• Examples: D-Bus control plugin, file-transfer plugin, segmentation plugin, viewer plugins, dummy/test plugins
• Plugins register commands, UI forms, filters, log storage backends, etc.
D. Data Sources & Sinks
• DLT log files (.dlt), pcap, MF4
• Live DLT daemon (via TCP/UDP/serial/D-Bus)
• Export targets (text, CSV, DLT)
• Project files (.dlp), filter files (.dlf)
E. Build & Deployment
• CMake (CMakeLists.txt in root, commander, parser, plugin, qdlt, src)
• Packaging scripts (scripts/{darwin,linux,windows})
• SDK generation (/sdk)
• CI workflows (.github/workflows/BuildPR.yml)
Relationships & data flow
• GUI/CLI ←→ Core Library
– GUI issues parse/load commands and displays filtered messages
– CLI issues parse/load/export commands in silent mode
• Core Library ▶ Plugin Manager ▶ Plugins
– On startup or on user request, core loads plugins from configured paths
– Plugins can register new filters, control commands, UI dialogs
• Core Library ↔ Data Sources
– Reads DLT files or connects to DLT daemon streams
• Core Library ▶ Exporters
– Writes out to text/CSV/DLT via internal exporter modules
• User actions (click/filter) ▶ GUI ▶ Core ▶ Model ▶ GUI update
Architectural patterns & design principles
• Layered architecture: Presentation / Application / Core / Plugins / Data
• Plugin pattern: dynamic discovery and loading via qdlt::PluginInterface
• MVC (Qt’s Model/View) in GUI for table display and filtering
• Observer pattern (Qt signals/slots) for event propagation
• Single-responsibility: each module (parser, exporter, UI dialog) encapsulates distinct functionality
• Dependency injection via interfaces (plugins talk to core through abstract classes)
Essential elements to capture
• Labels on each component (module name + path if needed)
• Plugin interface boundary between Core and Plugins
• Separation of GUI vs. CLI vs. Core vs. Plugins vs. Data
– two front-ends (GUI, CLI)
– a single, feature-rich core library
– a plugin ecosystem
– external data sources and sinks
– a unified build/deployment process.