How tonquer/picacg-qt works
Project type and purpose
• This is a cross-platform desktop client (“哔咔漫画PC客户端”) for browsing and downloading comics from the PicACG service.
• It uses PyQt (Qt) for its GUI, Python 3.9+ for business logic, and packages for Windows, Linux and macOS.
File structure
• Top‐level:
• src/ – main Python code
– component/ – custom Qt widgets (buttons, dialogs, sliders, frameless windows)
– interface/ – .ui files converted to Python: the raw Qt Designer forms
– view/ – MVC “views” that compose components and interface into screens (login, search, read, download, chat, settings…)
– server/ – internal HTTP server and API layer that mediates between GUI and data tasks
– task/ – background worker modules (download, convert, upload, SQL operations)
– db/ – local SQLite database (book.db)
– config/, tools/ – global configs and utility functions
– start.py – application bootstrapper
• script/ – build helpers for .ui, .qrc, translations, packaging
• README, CI workflows, packaging scripts (build_mac.sh), release assets
• This clearly follows an MVC/MVVM‐like pattern: UI forms + custom widgets (View), view classes (MVVM “ViewModels”), server/tasks (Controller), DB/files (Model).
README for additional insights
• Confirms: PyQt, waifu2x (GPU/Vulkan image upscaling), SQLite local cache, multi‐OS packaging.
• Highlights features: browse comics, download, read, chat, proxy support, themes, translations.
Elements
• Blue: Presentation (Qt)
• Green: Application Logic (server & tasks)
• Orange: Data (SQLite, config, resources)
• Gray: External Systems (PicACG API, waifu2x, SMB/WebDAV)
Detail
– Show the internal server’s handler modules (req.py, res.py, user_handler.py)
– Include build & packaging scripts off to one side (script/, build_mac.sh, CI.yml)