Create GUI Applications with Python Qt6 (Version 5.0, 2022-05-25, PySide6) (Martin Fitzpatrick)（Z-Library）

# Create GUI Applications with Python & Qt6 (PySide6) — Reading Guide ## 【One-Line Pitch】 A practical, project-driven guide to building desktop applications with PySide6 (Qt6 for Python), covering everything from basic widgets to custom painting, databases, and threading. Ideal for Python developers who want to create native-looking cross-platform GUI apps without learning C++. ## 【Book Arc】 - **Opening (~0%–12%)**: Foundations of Qt6 — creating your first window with QApplication and QWidget, understanding the event loop, and mastering core widgets (buttons, lists, text inputs) with signals and slots for interactivity. - **Early (~12%–28%)**: Dialogs, file handling, and window management — modal vs. modeless dialogs, QMessageBox patterns, file dialogs with overwrite protection, and showing/hiding windows. Introduces Qt Designer for visual UI layout and QRC resource files for bundling icons. - **Early–Middle (~28%–36%)**: Styling with Qt Style Sheets (QSS) — targeting widgets by type, class, or pseudo-states (hover, focus), understanding property inheritance, and the Model-View architecture with a first custom model (a todo list app). - **Middle (~36%–52%)**: Advanced Model-View patterns — custom QAbstractTableModel for tabular data, database integration with QSqlQuery and parameterized queries (with SQL injection protection), and bitmap graphics with QPainter for custom-drawn widgets. - **Late (~52%–end)**: Building a custom PowerBar widget from scratch, integrating custom widgets into Qt Designer via "Promote to" mechanism, and threading for keeping UIs responsive during heavy work. ## 【Key Takeaways】 - **Every Qt app needs a QApplication instance and an event loop** (Early): Create `app = QApplication(sys.argv)` (or `[]` if no CLI args needed), then `app.exec()` to start the loop. Top-level widgets are invisible until you call `.show()` — forgetting this is the #1 beginner mistake. - **Signals and slots are Qt's communication backbone** (Early): Widgets emit signals (e.g., `clicked`, `currentTextChanged`) that you connect to handler methods. Use the pattern of storing widget state in instance variables and updating them in handlers to keep your app's data in sync with the UI. - **Dialogs handle user interaction patterns** (Early): `QDialog.exec()` runs a modal dialog; `QMessageBox` provides ready-made critical/question/info dialogs with customizable buttons. For file operations, always check if a file exists before overwriting and confirm with the user — design for user mistakes. - **Qt Designer speeds up layout but has limits** (Early): You can visually design main windows and set stylesheets via right-click → "Change stylesheet…". However, custom widget properties can't be edited in Designer — you must set them in code, and use "Promote to…" to integrate custom widget classes. - **QSS styling is powerful but has quirks** (Early–Middle): You can target widgets by type (`QPushButton`), universal selector (`*`), or pseudo-states (`:hover`). But some properties (like `text-align`) don't work on certain widgets — use `.setAlignment()` instead. Style inheritance and specificity matter. - **Model-View architecture separates data from display** (Middle): A custom model subclassing `QAbstractTableModel` needs only `data()`, `rowCount()`, and `columnCount()` methods. Return `QColor` for `Qt.DecorationRole` to show color blocks, or use `Qt.BackgroundRole` for conditional formatting. - **QPainter enables custom-drawn widgets** (Middle): Bitmap drawing operations work on any surface (QPixmap, widgets). Master pen (outlines) and brush (fills) — remember to set a brush style or you'll get no fill at all. This is the foundation for building any custom widget, like the book's Paint app and PowerBar. - **Parameterized queries prevent SQL injection** (Middle): When using QSqlQuery with databases, always bind parameters (e.g., `album_title`) rather than concatenating strings into queries. This is both a security best practice and makes queries more maintainable. ## 【Reading Tips】 - **Skim the first 10% if you know basic Qt**: The opening chapters cover QApplication, QWidget, and simple widgets — move quickly to signals/slots and dialogs where the real patterns emerge. - **Deep-read the Model-View chapters (~36%–44%)**: This is the conceptual heart of the book. The todo list and table model examples are worth coding along with — they'll save you hours later. - **Don't skip the QPainter chapter (~48%)**: Even if you don't plan custom widgets, understanding bitmap vs. vector graphics and the painter API demystifies how all Qt widgets render. - **Use the code listings as your primary study material**: The book is code-first with explanations around listings. Type out the examples, run them, then modify them — the "Run it!" prompts are your best teacher. - **Watch for the "gotcha" callouts**: The book marks common pitfalls (invisible widgets, `NoBrush` default, Designer limitations) — these are the exact issues you'll hit in real projects. ## 【Coverage Limits】 This guide covers the core progression through widgets, dialogs, styling, Model-View, databases, and custom painting. The excerpts do not cover the threading chapter in detail, nor the later chapters on deployment/packaging — consult the book directly for those topics. ##