How kstickney/quote-system works
Project type and purpose
• This is a standalone Python-based desktop quoting system (“Business Quote System”).
• Purpose: let a small business create, store, and export customer quotes (PDFs) using local data and optionally scrape vendor prices from the web.
High-level architecture and main components
We will represent the system as a layered, modular desktop application with these primary components:
A. Presentation Layer (Desktop GUI)
– Quote_System.py (main entry point)
– PyQt/Qt styles & resources (styles/, stylesheets/, fonts/, images/)
B. Business Logic Layer
– CustomClasses.py (domain-specific objects: Quote, LineItem, Settings)
– pdf/pdfcreator.py + jinja2 templates (quote-template.html.j2)
– web_scraping/ (optional service to fetch prices)
C. Data Access Layer
– database.py (Access .accdb integration)
– Pickle files under data/ and “Fresh Pickle Files” (settings, database snapshot)
D. External Tools & Services
– wkhtmltopdf.exe & wkhtmltoimage.exe (PDF renderer)
– pyinstaller (for packaging .exe)
– Access Database driver (OLEDB/ODBC)
E. Cross-cutting Concerns
– Logging (app.log)
– Configuration files (pylintrc, Makefile, .github/workflows/ci.yaml)
– Build & packaging (setup.py, requirements.txt)
Relationships and data flows
• User → GUI: triggers “New Quote,” “Load Quote,” “Generate PDF,” “Fetch Prices.”
• GUI → Business Logic: passes domain objects to CustomClasses, invokes PDF creator and scraper.
• Business Logic → Data Layer: reads/writes quotes and settings to .accdb and pickles.
• PDF Creator → External Tool: renders HTML via wkhtmltopdf to generate final PDF.
• Web Scraper → External Sites: scrapes industrial automation price data, returns to business logic, and persists to database.
• All modules write to app.log for audit/troubleshooting.
Architectural patterns & design principles
• Layered (Presentation → Business → Data → External).
• Separation of concerns: styling in dedicated directories; logic in CustomClasses & pdfcreator; data access abstracted in database.py; external integration encapsulated.
• Resource bundling: Qt resource files (.qrc) map images/fonts into GUI.
Final checklist
– All components clearly labeled.
– A note on build process (PyInstaller) and CI (ci.yaml) for completeness.