There are very few examples online of QML using PySide2 as a backend, so I decided to start collecting some simple ones while I learn this technology. I think QML is a great idea that clearly separates logic from presentation, so hopefully people in VFX and Animation will start using it (instead of handling all of the .ui to .py autogenerated code madness).
I've read online about QML from people in VFX and there is a certain sentiment that it's only for creating fancy "mobile-like" experiences. In my humble opinion, they really aren't getting the big picture...
-
I don't like looking at your 1000 lines of autogerated UI code just to get a feeling of the underneath data model
-
No need to use QtDesigner/QtCreator. Iterating a UI mockup is simple enough via
qmlsceneand vim, neovim, vscode, etc. -
It makes it easier to make edits on the presentation layer without touching the python code
-
You can create components that define a certain look/behaviour and reuse them (buttons but even lists views, menu bars, etc..)
-
Yes, It's still a little bit of a PITA to use QML inside Nuke/Maya/Houdini, but things are slowly changing. In the meantime, nothing prevents you from doing standalone apps in QML, as long as you've got ways to properly package/source PySide2 (rez, conda, pip, tcl-modules, etc..)
-
If you're crazy enough and you realize in the mid of a project that you need more performance for the backend, you could potentially rewrite it in C++ and leave the frontend almost untouched
-
Great UI performance thanks to the new QtQuick Scene Graph which greatly reduces draw calls (https://doc.qt.io/qt-5/qtquick-visualcanvas-scenegraph.html)
-
It finally offers TreeViews and TreeModels!
-
You need to learn something new (pros for some, con for others)
-
There's not really a lot of huge amount of documentation for Python as a backend (but if you're here we can change that!)
-
You might find it harder to tweak some of the UI elements exactly as you'd like to
-
As a framework, it's not as old and mature as QtWidgets, so expect things to change or be deprecated between versions
This is really useful for prototyping a UI without wanting to write a main.py at all.
$ qmlscene main.qml- The official Qt website is a great reference: https://doc.qt.io/qt-5/qmlapplications.html
- Youtube series by KDAB: https://www.youtube.com/watch?v=JxyTkXLbcV4
- Udemy course for beginners: https://www.udemy.com/course/qt_quick_qml_tutorial_for_beginners/
Note: The following examples have been tested under python3.7 and pyside2=5.13.2.
They should also work under python2.7, but I haven't tested that
Very simple example showing how to populate a 1d list-view using a model.
Slightly more complex example showing how to implement a basic app that uses threads and signals to perform a long blocking calculation without blocking the UI. Also shows an example of a 2d list view where each row item contains sub items.
Boiler-plate code that shows how you could integrate drag & drop and some parsing logic in order to fill a list view. This could be for example used as the start of an app for publishing frames
An example of an application launcher where updating a dropdown menu causes the update of the others. Uses a reusable ContextDropDown qml component that works with a standard ListModel with a custom delegate.
As always, PRs are welcome! There are different types of contributions that you could make. For now, I think that those would be nice:
- Improve the wiki! (which is empty, at the moment)
- Improve the readme
- Add relevant links where people can learn more about PySide2 + QML
- Start an issue to discuss about something relevant to everybody (IE: how the heck can I use this workflow in Nuke?)
- Improving the existing examples to make it easier to follow through
- Add more generic examples to showcase different usage scenarios (I'd love to see a Text autocompleter implemented in Qml!)
- Check on all OS (I can only test on macOS and Centos 7.7!)
- Write tests