Details
-
Task
-
Resolution: Done
-
P4: Low
-
5.7
Description
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).
Attachments
Issue Links
- depends on
-
QTBUG-96800 deprecate and later remove the qml (and qmlscene) --dummy-data argument
-
- Closed
-
-
QTBUG-53557 ensure that the qml runtime is really a suitable replacement for all qmlscene use cases
-
- Closed
-
- is duplicated by
-
QTBUG-65862 documentation: remove most mentions of qmlscene, use qml instead
-
- Closed
-
- is required for
-
QTBUG-95302 Update/overhaul QML documentation
-
- Closed
-
- relates to
-
QTBUG-33659 set qml tool as the system viewer for qml files
-
- Reported
-
-
QTBUG-82340 Consider which qml tools to deprecate/unify in Qt 6
-
- Withdrawn
-
For Gerrit Dashboard: QTBUG-53219 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
373730,4 | WIP add back information about qml's options, with details about import path | dev | qt/qtdoc | Status: NEW | -2 | 0 |