I didn't mean in any way that QML was a worse solution than what qt4 offers. More that it's not accessible (not shipping along with current 3d software) so it

I didn't mean in any way that QML was a worse solution than what qt4 offers. More that it's not accessible (not shipping along with current 3d software) so it is off the radar for most people. 6 months ago I was at a place where all code had to be compatible with Python 2.6 (we had moved off of Python2.5 only a year or so before). When I've looked at playing with PySide2 using Python2 I see that it's not there yet.[1] I feel like I'm in the minority of people I work with who have even seen Python3, let alone know what features it has. At my current place we don't compile anything. Most of the work I see are forms, running inside 3d software, that are basically arguments for a process...maybe read from a database or your local scene/environment. Designer UI files or hand-written UIs seem to be good enough for most people (it's way better than the alternative scripting UIs used before Qt). It needs to run inside and outside of Maya and other packages, which usually means is compatible with Python 2.6 and 2.7, likely need to support PyQt and PySide, and might need to work in Linux and Windows (ideally following that OS' conventions). Performance isn't a huge concern since loading the data takes way more than drawing the UI. Also, people are really averse to learning a new language. The understanding I had for qt5 was focusing on UI elements for alternate devices like cellphones and touch. While a lot more flexible, in many cases you'd have to reimplement normal UI widgets from lower-level pieces. At the same meeting, the few people familiar with QML were asking about getting a QML Tree View. I'm curious to know more about qt5, but like Python3, it's currently not an option. [1] https://github.com/PySide/pyside2/wiki https://github.com/PySide/pyside2/wiki