Details
-
Task
-
Resolution: Done
-
P1: Critical
-
None
-
1eb20d70619cc896fc283bd6605b257a8750c518 c5b48c735e1c26444e53c4ea7dc6df4c57b5e9b4
Description
We want to make the versioning in Qt Quick less confusing. One part needed is to add version information in Qt Quick plugins in the data section, so we can determine the latest version of each plugin. Enable "Import Qt Quick 2" and you'll get the latest. Then move our examples over to this scheme.
In addition to a "find the latest version" import with only the major number we also need an import statement that propagates the exact version of the parent document, so that a Component from, say, Qt Quick Controls can derive from a another control while preserving the version information given from the outside. This is so that the component finally exposed to the user doesn't contain properties from the component derived from that were only added in versions after the one specified by the user. One idea for a suitable syntax would be "import QtQuick auto".
Attachments
Issue Links
- is required for
-
QTBUG-65266 Interaction between FINAL and REVISION on a property don't fully make sense
- Open
-
QTBUG-73259 New AbstractButton 'icon' property in QtQuick.Controls 2.3 affects code with older version imports
- Open
-
QTBUG-80788 [5.14 REG] New properties in ComboBox clash with custom properties (revision ignored)
- Closed
- relates to
-
QTBUG-77532 Establish a language versioning mechanism for QML
- Closed