Python GUI with PyQt - Learn to build modern and stunning GUIs in Python with PyQt5 and Qt Designer (Saurabh Chandrakar etc.)（Z-Library）

【One-Line Pitch】 A hands-on, beginner-friendly path to building desktop GUIs in Python with PyQt5 and Qt Designer, taking you from your first window to model-based item views. Best for Python programmers who know the language but have never shipped a real interface. 【Book Arc】 - **Opening (~0%–11%)**: Sets up the toolkit — why PyQt5, how it relates to the authors' earlier tkinter book, and how to install Qt Designer (via `pyqt5-tools`, not plain pip). Solves the "where do I even start" problem. - **Early (~11%–25%)**: Core mechanics: creating windows, the `.ui` → `.py` conversion workflow with `pyuic5`, and the crucial rule that generated code must never be hand-edited. Introduces layout managers (horizontal, grid, form) and stretch behavior. - **Early (~25%–36%)**: Event-driven programming proper — signals and slots, mouse events, and connecting widget signals to custom slots. This is the conceptual hinge of the whole book. - **Middle (~36%–50%)**: Widget survey: buttons (push, tool, check, radio), their properties, methods, and signals, plus sizing policy and input-method hints. Moves from "make a window" to "make a usable form." - **Middle (~50%+)**: Item views and the Model/View framework — list, tree, table, and column views, `QAbstractItemView`, and `QStandardItemModel`. The excerpts do not cover the later display-widget and container material in detail. 【Key Takeaways】 - **Qt Designer plus `pyuic5` is the book's central workflow** (Early): you design visually, generate Python, then write a separate `run_*.py` file that imports and drives the generated UI. Internalizing this split early makes every later chapter easier. - **Never edit generated `.py` files by hand** (Early): any manual change is overwritten the next time you regenerate from the `.ui` file. Keep your logic in the runner file instead. - **Signals and slots are the cornerstone of event-driven PyQt** (Early): a widget's `clicked` signal connects to a slot method, which fires on user action. Everything interactive in the book builds on this pattern. - **Layout managers, not fixed coordinates, control placement** (Early): horizontal, grid, and form layouts, plus `addStretch`, determine how widgets share space and resize gracefully. - **Widgets come with a deep property/method/signal surface** (Middle): the book catalogs these systematically — e.g. `QCheckBox`'s `tristate`, `stateChanged(int)`, and `setIcon()` — so you learn to look up rather than memorize. - **Size policy governs resize behavior** (Middle): flags like Expanding and Ignored, combined with `sizeHint()`, explain why widgets grow, shrink, or stay fixed. - **Item views follow a Model/View architecture** (Middle): `QTreeView` and `QTableView` render data from model classes, and views update automatically when the model changes — a different mental model from plain widgets. - **Each chapter ends with practical examples and exercises** (throughout): the book is explicitly interactive, so the code bundle is part of the learning method, not an appendix. 【Reading Tips】 - Deep-read the `.ui` → `.py` → `run_*.py` cycle in the early chapters; it is the workflow every later example assumes. - Skim the long property/method/signal tables on a first pass and return to them as reference when a specific widget misbehaves. - Type and run the examples rather than reading them — the annotated line tags (e.g. `SS_3`, `QTBEG1_4`) only pay off when you trace them in working code. - Treat the signals-and-slots chapter as the hard conceptual stop; if it clicks, the widget chapters become mostly vocabulary. - Keep the official Qt documentation link the book cites handy for anything the excerpts leave thin. 【Coverage Limits】 The excerpts are heavily weighted toward the opening through the item-views chapter; dialog/message boxes, containers, and display widgets are mentioned in the blurb but not substantively covered here, so this guide's later-stage mapping is approximate.