Is QML translated into native code at the compilation time or is it interpreted at runtime almost the way JavaScript is ran in a web browser?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Is QML translated into native code at the compilation time or is it interpreted at runtime almost the way JavaScript is ran in a web browser?
AFAIK, there seem to be no straight and detailed explanation in the Qt documentation, but some Qt hackers try to explain it:
There also is related QTBUG task QtQuick startup time needs to be improved; cache compiled QML between runs
My understanding is that QML status hasn’t been settled completely and engineers don’t declare it fixed, so they have freedom to improve it in future.
ATM, it best advice is to mix C++ with QML, having all application logic in C++ and presentation in QML, but ideally divided into smaller QML files, not in a single large QML file.