> That's not a fair question.
> Obviously QML cannot be faster than the equivalent, well-written C++.
The question here is not if QML is faster. That is obvious.
The question is how much QML is slower then native C++.
As i said before, using border images in stylesheets
increase e. g. the cpu load from 4% to 28%. That happens,
because this feature is badly implemented in QT.
So it would be very interesting to compare QML with C++.
If the cpu load is 1% higher or QML is a little bit slower,
i would not care.
What i would like to see if the QT developers first fix
existing bugs before implement new features.
- Styling border and transparency of QTableView.
- Elide mode in styled QHeaderView.
- Styling of QHeaderView.
> The biggest advantage QML is going to give you is the ease of writing your
> both in terms of time spent, the flexibility to change, and the fact that
> you're building on top of an optimised stack for doing the UI.
The model / view concept of Qt is one of the advanced technologies.
Nonetheless there are some bottlenecks that results in inhereited
classes of QItemDelegate, QTableView, QSpinbox, ... .
If you want a component that acts like excel, this is going worse.
In C++ you can do that. what's about QML?
As i said before, i don't know enough about QML.
As an embedded developer i know about platform limitations and from my
point of view, the OP has to make a analysis on his platform to check
if QML is worse to give it a try.
Qt-interest mailing list