This demo is not as fancy as my previous work yet simply because of the steep learning curve with QML involved, but it’s work in progress and I am very impressed with the graphical performance so far.
The tool I am working on here have been planned and attenpted a few times with different technology. I could have completede it in different technology earlier, but as I target SCADA/HMI solutions I am picky about graphics performance. QML is the most promissing so far, but it slower to work with than the alternatives (yet). That said I have no performance issues as the GPU’s does the heavy work and I have full graphical freedom. I also expect that this will be easier to work with as my experience level on QML grows.
Dealing with QML you have to deal with 4 layers of different languages and the integration between them.
- C++ versus Qt’s version of C++. Qt can use ordinary C or C++, but Qt libs have so many additions and tweaks that you end up converting data and signals. This is a pain if you like me write code to be used as firmware components as well.
- Bindings between C++ and QML. On this step I think Qt have done a good job, but it is manual work.
One of the advantages with QML is that it supposedly alwo runs on Web, Windows, Linux, Android etc – so far I have only tested Windows, but I wil be testing raspberry PI’s.
Well done Qt!