https://www.youtube.com/watch?v=2nnrl1v7LcE explains why we have it: it is intended to be an ordinary script interpreter, like perl or python; it should not load modules (like widgets) until you need them; it handles the shebang mechanism; and it is intended as the canonical way to run a QML file, even for end-users. Yet the docs still mention using qmlscene for testing/debugging applications, and don't mention the qml tool at all AFAICT. There also needs to be documentation of what can be achieved with custom config files (tools/qml/conf/configuration.qml is the default, but we have no alternative examples).
|For Gerrit Dashboard: QTBUG-53219|
|373730,4||WIP add back information about qml's options, with details about import path||dev||qt/qtdoc||Status: NEW||-2||0|