How stredes/exelcior_apolo works
Project type and purpose
• Exelcior Apolo is a cross-platform, desktop Python application with a graphical UI (Tkinter) that automates Excel file transformation, validation, preview and printing. It supports multiple “modes” (FedEx, Urbano, Listados, Inventario, Etiquetas), persists history in SQLite, and invokes platform-specific printer services (Excel COM on Windows, LibreOffice on Linux/macOS).
File structure
• Top-level:
• app/: contains all application code, subdivided into
– config/: configuration loading/editing, JSON defaults
– core/: Excel processing, transformation rules, logging events
– db/: SQLAlchemy models, DB connection, SQLite file
– gui/: Tkinter windows and dialogs per mode
– printer/: mode-specific print/export logic and platform drivers
– services/: file detection/auto-load routines
– utils/: path, platform detection, logger setup, validations
• main_app.py & run_app.py: bootstrap the application
• assets/version: versioning metadata
• data/: packaged SQLite DB, JSON
• installer/: Inno Setup definitions, output installers
• build & spec files: packaging scripts
• tests/: pytest files testing printer modules and dry-runs
• requirements.txt: dependencies
README for additional insights
• Architecture hints:
• Modular modes — each mode as independent component
• Persistence layer via SQLAlchemy + SQLite
• Excel processing via pandas/openpyxl
• Printing via external services (Excel COM, LibreOffice)
• Preview + export to PDF (ReportLab)
Elements
• Green for core processing modules
• Orange for persistence
• Gray for external dependencies/services
Detail-level advice
• Explicitly show the branching to Excel COM vs. LibreOffice based on platform_utils
• Config JSON file location and how Config Manager abstracts it