Qt-contributors-summit-2013-Evolution-of-the-QML-language: Difference between revisions

@@ Line 1: / Line 1: @@
-=Forward Versioning Control=
-Uses Qt versions, meaning no new features in patch releases.
-For features that won’t provide good errors, consider using pragmas to enforce a clear error message at the top of the files
-=Impending Features=
-Targeting 5.2
-==Pragmas==
-new “pragma foo” lines will be added. pragma lines must come in the preamble before all item declarations, and some might require being placed before import lines. Note that unlike <span class="caps">QML</span>/JS files, there is no “.” before the line. Example:<br />
-==Singletons==
-New “pragma singleton” makes this <span class="caps">QML</span> file represent a type which is a singleton type. Behavior of type is identical to C++/JSValue singletons.
-Example:
-=Long term features=
-No schedule yet. Note that attached properties are currently planned to be left with C++ as an advanced usecase.
-==Enums in <span class="caps">QML</span>==
-Something like <br />
-==Grouped properties in <span class="caps">QML</span>==
-Something like<br /> Where CustomObject is a QObject derived type, and the non-optional initializer provides a default value which is copied on write.
-==const properties==
-==pragma strict==
-Mostly like JS pragma strict, may provide even more type safety by denying implicit conversions (if we add explicit conversions of course).

Revision as of 13:57, 24 February 2015