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.
Performance tip Use Loaders: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(Cleanup) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
[[Category:Developing_with_Qt::Qt Quick]] | {{LangSwitch}} | ||
[[Category:Developing_with_Qt::Qt Quick]] | |||
[[Category:Developing_with_Qt::Performance Tips]] | |||
Note: See also [http://doc.qt.io/qt-5/qml-qtquick-loader.html http://doc.qt.io/qt-5/qml-qtquick-loader.html] | |||
QML applications can start slowly if there is a lot of QML to be parsed. This can happen if the whole application is implemented in one huge QML file. Partition our application wisely into logical entities, load minimum QML at start and load more as you need it using Loaders. | QML applications can start slowly if there is a lot of QML to be parsed. This can happen if the whole application is implemented in one huge QML file. Partition our application wisely into logical entities, load minimum QML at start and load more as you need it using Loaders. | ||
* The Loader item can be used to dynamically load and unload visual QML components defined in a QML file or items/components defined within a QML file. This dynamical behavior allows the developer to control the memory usage and startup speed of an application. | * The Loader item can be used to dynamically load and unload visual QML components defined in a QML file or items/components defined within a QML file. This dynamical behavior allows the developer to control the memory usage and startup speed of an application. | ||
* Partition your application into several QML files so that each file contains a logical UI entity. This way loading and unloading are easier to control. DO NOT have one huge QML file per application. | * Partition your application into several QML files so that each file contains a logical UI entity. This way loading and unloading are easier to control. DO NOT have one huge QML file per application. | ||
* Load absolutely minimum amount of QML at application start to make your application start as quickly as possible. You can connect to network and show spinner etc. after the application UI is visible. | * Load absolutely minimum amount of QML at application start to make your application start as quickly as possible. You can connect to network and show spinner etc. after the application UI is visible. | ||
* If your first view is very complex and requires lots of QML to be loaded, show a splash screen to give user the feeling that something is happening | * If your first view is very complex and requires lots of QML to be loaded, show a splash screen to give user the feeling that something is happening | ||
* You should load pieces of UI only by demand e.g. when the user navigates to another view, but on the other hand it may require more time to navigate between views | * You should load pieces of UI only by demand e.g. when the user navigates to another view, but on the other hand it may require more time to navigate between views | ||
Latest revision as of 21:27, 28 June 2015
En Ar Bg De El Es Fa Fi Fr Hi Hu It Ja Kn Ko Ms Nl Pl Pt Ru Sq Th Tr Uk Zh
Note: See also http://doc.qt.io/qt-5/qml-qtquick-loader.html
QML applications can start slowly if there is a lot of QML to be parsed. This can happen if the whole application is implemented in one huge QML file. Partition our application wisely into logical entities, load minimum QML at start and load more as you need it using Loaders.
- The Loader item can be used to dynamically load and unload visual QML components defined in a QML file or items/components defined within a QML file. This dynamical behavior allows the developer to control the memory usage and startup speed of an application.
- Partition your application into several QML files so that each file contains a logical UI entity. This way loading and unloading are easier to control. DO NOT have one huge QML file per application.
- Load absolutely minimum amount of QML at application start to make your application start as quickly as possible. You can connect to network and show spinner etc. after the application UI is visible.
- If your first view is very complex and requires lots of QML to be loaded, show a splash screen to give user the feeling that something is happening
- You should load pieces of UI only by demand e.g. when the user navigates to another view, but on the other hand it may require more time to navigate between views