Details
-
Epic
-
Resolution: Out of scope
-
P3: Somewhat important
-
None
-
6.0
-
None
-
QmlSpec
-
Description
Over the last years we learned a lot about how QML should be designed. Many iterations have been done.
With Qt Quick Ultralite, we are now facing a situation that two implementations of the language (and items) exist. To guarantee compatibility between the two, we want to agree on patterns and formally mark them.
First of all, a QML language specification document is required. The content of this document should cover topics like syntax, semantics, etc.
Furthermore, the aim is to have additional companions describing default and optional sets of items and properties for these. Starting from these specifications QUL can define their scope (target is to fully support the default and increasing amount of optional), while QML as available in Qt will cover all cases.
Mid term it will help developers and users to understand the scope and features of all implementations in existence.
Attachments
Issue Links
- relates to
-
QTBUG-16062 Add list of reserved words not to be used as QML ids
- Open