How oskarowski/imagio-image-processing-app works
Project type and purpose
• This is a Go-based, monolithic image-processing application with two user interfaces:
• A CLI front-end (cmd/cli_app.go + cmd/executioner)
• A TUI front-end (cmd/tui + internal/ascii_preview)
• Core business logic resides in package directories: manipulations, morphological, noise, orthogonal_transforms, analysis, imageio, reporting.
File structure
• Top-level UIs:
• cmd/cli_app.go + cmd/executioner/* → CLI command definitions & handlers
• cmd/tui/* + internal/ascii_preview → TUI screens, helper renderers, input forms
• Core engine packages:
• imageio → BMP file read/write
• manipulations → pixel-level operations (brightness, contrast, geometric…)
• morphological → dilation, erosion, thinning, region growing
• noise → synthetic noise generators/filters
• orthogonal_transforms → Fourier, bandpass, mask filters
• analysis → histogram, comparison metrics
• reporting → execution reports, performance metrics
• Assets & configuration:
• assets/cli, assets/tui → example images, TUI sprites
• masks.json, structure_elements.json → filter configurations
README
• Confirms dual‐mode operation (CLI vs TUI)
• Lists all commands and parameters
• No external services or databases—purely file-based I/O
Main components & interactions
a. Front-ends (CLI, TUI)
b. Command Dispatcher/Executioner
c. Core Processing Engine (sub-modules for manipulations, morphological, noise, transforms, analysis)
d. Image IO (read/write BMP)
e. Reporting (command metrics, durations)
f. Configuration/data stores (masks.json, structure_elements.json, built-in assets)
g. File System (imgs/, output files)
Architectural pattern
• Layered architecture with clear separation:
UI layer → Dispatcher layer → Business logic layer → IO layer
• Command pattern in cmd/executioner for pluggable handlers
• Modular package structure for extensibility