How dimanikulin/fva works
Project Type and Purpose
• This is a desktop‐based, multi‐module “convergent tool set” for automating the import, enrichment, organization, and transfer of multimedia data (photos/audio/video) into online/offline multimedia IR systems (e.g., digiKam, Synology Moments).
• It comprises C++ Qt GUI applications, command‐line C++ processors, Python maintenance scripts, a shared C++ library, plus packaging and resource files.
File Structure Analysis
• Top-level modules (each with its own CMakeLists):
• FVACommonLib – core functionality (CSV, Exif, configuration, logging, dictionary).
• FVAConfigurator – QtWizard UI for configuring flows.
• FVADataProcessor – CLI tasks to validate/transform files.
• FVADescriptionEditor, FVADictionaryEditor – Qt GUI editors.
• FVAFlowController – orchestrates device contexts and processing steps.
• FVAOrganizer / FVAOrganizerWizard – wizards and simple organizer UIs.
• FVAPlayer, FVAViewer – media playback and filtering.
• scripts/ – Python scripts for ad-hoc tasks (metadata fixes, DB creation).
• test/, and per-module test/ directories – unit/integration tests.
README Insights
• Context view: external devices → FVA Solution → multimedia IR systems.
• Functional view: Layered architecture (UI → Processing → Data & Configuration).
• Deployment view: bin/, data/, logs/, scripts/ directories at install.
Main Components & Their Interactions
a. External Entities (Context):
• Photo-video sources: tablets, phones, cameras, external disks.
• End Targets: Offline IR (digiKam), Online IR (Synology Moments, Google Photos).
b. FVA Solution – Logical Subsystems:
1. UI Layer (Qt Apps):
• Configurator (QTWizard)
• DescriptionEditor, DictionaryEditor (Qt Designer UIs)
• Organizer Wizard
• Viewer, Player
2. Processing Layer (C++ CLIs + Flow Controller):
• FVADataProcessor and its CLT* commands
• FVAFlowController orchestrating tasks based on configuration
3. Data & Configuration Layer:
• FVACommonLib (CSV, Exif parsing, logging, constants, dictionary items)
• application configurations (fvaconfiguration)
• scripts (Python tools using CSV, Exif, DB scripts)
c. External Services:
• File system for input and output folder structures
• Packaging subsystem for building installers (WiX for Windows)
Architectural Patterns & Principles
• Layered Architecture: UI → Processing → Data/Config
• Modularization: Each tool in its own directory with isolated CMake build.
• Reuse via common library (FVACommonLib) and consistent command‐line base classes.
• CI/CD workflows (.github/workflows) for tests, code checks, documentation, release.
• Testability: each module has unit tests; integration tests under test/integration.