Qt-contributors-summit-2012-QMLTooling: Difference between revisions
Jump to navigation
Jump to search
AutoSpider (talk | contribs) (Simplify punctuation) |
m (Categorize) |
||
| Line 1: | Line 1: | ||
{{Cleanup | reason=Auto-imported from ExpressionEngine.}} | {{Cleanup | reason=Auto-imported from ExpressionEngine.}} | ||
[[Category:QtCS2012]] | |||
1) Qml Designer for QtQuick 2 is needed, especially in combination with Qt Quick Components. There is a major use-case for this feature. The existing Qml Designer for QtQuick 1 was well appreciated.<br /> 2) Call graph would be good-to-have.<br /> 3) Memory profiling. Especially, one which shows an overview of live objects versus time.<br /> 4) The <span class="caps">QML</span> Tools are relatively unknown and hence they are mostly not used. They need to be "advertised". <br /> 5) <span class="caps">GPU</span> profiling is not so important, animation profiling already covers the simple cases. | 1) Qml Designer for QtQuick 2 is needed, especially in combination with Qt Quick Components. There is a major use-case for this feature. The existing Qml Designer for QtQuick 1 was well appreciated.<br /> 2) Call graph would be good-to-have.<br /> 3) Memory profiling. Especially, one which shows an overview of live objects versus time.<br /> 4) The <span class="caps">QML</span> Tools are relatively unknown and hence they are mostly not used. They need to be "advertised". <br /> 5) <span class="caps">GPU</span> profiling is not so important, animation profiling already covers the simple cases. | ||
Latest revision as of 17:09, 6 January 2017
| 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. |
1) Qml Designer for QtQuick 2 is needed, especially in combination with Qt Quick Components. There is a major use-case for this feature. The existing Qml Designer for QtQuick 1 was well appreciated.
2) Call graph would be good-to-have.
3) Memory profiling. Especially, one which shows an overview of live objects versus time.
4) The QML Tools are relatively unknown and hence they are mostly not used. They need to be "advertised".
5) GPU profiling is not so important, animation profiling already covers the simple cases.