Qt wiki will be updated on October 12th 2023 starting at 11:30 AM (EEST) and the maintenance will last around 2-3 hours. During the maintenance the site will be unavailable.
Qt-contributors-summit-2014-QtCs14MoreDeclarative: Difference between revisions
No edit summary |
AutoSpider (talk | contribs) (Add "cleanup" tag) |
||
| Line 1: | Line 1: | ||
{{Cleanup | reason=Auto-imported from ExpressionEngine.}} | |||
=Declarative <span class="caps">QML</span>= | =Declarative <span class="caps">QML</span>= | ||
Revision as of 16:33, 3 March 2015
| This article may require cleanup to meet the Qt Wiki's quality standards. Reason: Auto-imported from ExpressionEngine. Please improve this article if you can. Remove the {{cleanup}} tag and add this page to Updated pages list after it's clean. |
Declarative QML
It should be declarative. Let’s make the dream come true! What specific, constructive changes can we make to help this happen without breaking everyone (and without making things impossible).
Maybe just better
Specific API issues
Changing State
StateChange element: like https://codereview.qt.io/#change,3356
Loader/Repeater
It interrupts the hierarchy of objects, but main problem is that it’s getting abused.
Deferred loading flag on Item would fix the not-really-dynamic case where they shouldn’t be using Loader. And tools can override the flag somehow.
Signal Handlers
Pull model basically solves this in the cases where it’s abused.
Could expose Polish, which might also solve it in specific cases.
Translation
DONE! If it’s not in a complex expression of course.
Strictly Declarative Mode
Of some interest, but needs more actual use-cases that it would solve before being worth the effort.
Declarative Transactions (Atomic/Pull bindings)
Good idea. Tons and Tons of work.