Designing UIs with Qt Quick 5/6, Animations Part 2
summary
Three UI templates and concrete patterns: use a single main screen when layout never changes, a fixed menu plus visual item model when inner screens swap, and a Loader element when screens load on demand so only the home screen plus one other occupy memory. Animations use opacity behaviors; complex state machines (one project had ~100 screens) move from QML to C++ for maintainability. Qt Creator debugs JavaScript only. A working QML introspection tool Gamray on GitHub exists for runtime inspection.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 0:40Single Main Screen
- 1:05PDF Reader
- 2:40Single Screen
- 4:23Fixed Main
- 8:47Multiple Screens
- 12:38Experience
- 15:17Qt for Complex Projects
- 15:55Logic
- 16:56Reusable
- 17:11Example
- 18:34Extract Components
related talks
24mThe Roadmap: Next Generation Qt (part 2/2)
55mUI Design for Small Screen Devices
23mQt Quick : Don't make these mistakes!
25mBest Practices for using QML and QtQuick
30mThe building blocks of QML, and how to use it with C++
46mQt Quick Controls Re engineered
27mSet Yourself up for Success — Lessons Learned from Building 100+ Devices with C++/Qt/QML
49mHow to scale QML based projects an Architecture vision