https://wiki.qt.io/index.php?title=Qt_Contributor_Summit_2019_-_QtQml&feed=atom&action=historyQt Contributor Summit 2019 - QtQml - Revision history2024-03-29T01:55:37ZRevision history for this page on the wikiMediaWiki 1.39.4https://wiki.qt.io/index.php?title=Qt_Contributor_Summit_2019_-_QtQml&diff=36484&oldid=prevEdwardWelbourne: Add to category QtCS20192019-11-22T15:27:40Z<p>Add to category QtCS2019</p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 15:27, 22 November 2019</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l1">Line 1:</td>
<td colspan="2" class="diff-lineno">Line 1:</td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">[[Category:QtCS2019]]</ins></div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>Grouped properties</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>Grouped properties</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>------------------</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>------------------</div></td></tr>
</table>EdwardWelbournehttps://wiki.qt.io/index.php?title=Qt_Contributor_Summit_2019_-_QtQml&diff=36461&oldid=prevUlf Hermann: Created page with "Grouped properties ------------------ Grouped properties are incredibly buggy and basically unusable for anything but font and anchors right now. The language would be bette..."2019-11-22T08:40:25Z<p>Created page with "Grouped properties ------------------ Grouped properties are incredibly buggy and basically unusable for anything but font and anchors right now. The language would be bette..."</p>
<p><b>New page</b></p><div>Grouped properties<br />
------------------<br />
<br />
Grouped properties are incredibly buggy and basically unusable for <br />
anything but font and anchors right now. The language would be better <br />
off without the concept, allowing only the replacement of the full <br />
object (e.g., hypothetically, with inline components: "font: MyText.Font <br />
{ bold: true }") rather than individual grouped properties. The <br />
semantics of such would be easier to understand and easier to implement, <br />
but people don't like this, of course.<br />
<br />
https://bugreports.qt.io/browse/QTBUG-72164<br />
<br />
<br />
Context properties<br />
------------------<br />
<br />
These are remarkably evil and actually unnecessary. You can readily <br />
replace them with singletons or object properties (possibly required <br />
ones) already in 5.15. We can deprecate context properties.<br />
<br />
https://bugreports.qt.io/browse/QTBUG-73064<br />
<br />
<br />
Versioning<br />
----------<br />
<br />
Once we get rid of unqualified lookups we don't need any QML versioning <br />
anymore. At least the minor version will become optional already in 5.15 <br />
for well-behaved QML documents. In QML 3 it won't be allowed.<br />
<br />
<br />
Warnings / Transition to QML 3<br />
------------------------------<br />
<br />
We need a way of fine tuning the warnings. If you intend to port your <br />
program to QML 3 you want to see all deprecation warnings. If not, you <br />
want to suppress them all. If you want to stay with QML 2 but still fix <br />
some of the more glaring problems in your code, you may want to enable <br />
some warnings, but not others. We can have pragmas declaring what your <br />
code aims for in the QML files themselves and environment variables to <br />
switch warnings on or off. (In fact we want logging categories, but we <br />
didn't talk about that). We're not going to add replacement <br />
functionality (e.g. required properties) to 5.12 anymore. The base for <br />
porting to QML 3 has to be Qt 5.15.<br />
<br />
<br />
Smart pointer support<br />
---------------------<br />
<br />
We want QML to properly deal with smart pointers. For example, it should <br />
be possible to transfer ownership by moving a unique pointer.<br />
<br />
https://bugreports.qt.io/browse/QTBUG-60136<br />
<br />
<br />
Sequence types<br />
--------------<br />
<br />
We need a way to register your own container classes with the QML engine <br />
so that they behave the same way as certain auto-registered lists and <br />
vectors do. Also, people would like something akin <br />
to QQmlListProperty in qtbase. That is, a lightweight "model" that just <br />
grants access to some sequence data without providing storage for it.<br />
<br />
https://bugreports.qt.io/browse/QTBUG-71574<br />
<br />
Typed Model Data<br />
----------------<br />
<br />
We brainstormed a bit about how a model could declare its items' data <br />
type in QML, so that we could statically check model against delegate <br />
types. We will need this when compiling QML 3 to C++. We didn't come up <br />
with anything really great, though. This needs more work.</div>Ulf Hermann