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.

Utilizing-Qt-Quick-Colibri-in-PySide: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
No edit summary
 
(Rename category "LanguageBindings::PySide" -> "PySide")
 
(5 intermediate revisions by 3 users not shown)
Line 1: Line 1:
=Utilizing Qt Quick Colibri in PySide=


This [[PySide]] tutorial takes an existing PySide <span class="caps">QML</span> application that uses a totally custom UI, and shows how such an UI can be transformed to use a pre-made component library. In the future, it will be useful to use [[Qt-Quick-Components|Qt Quick Components]], but as it’s not ready yet, we are using the open source [https://projects.developer.nokia.com/colibri/ Qt Quick Colibri] ''[projects.developer.nokia.com]'' library. The existing application that we are modifying for this is the '''WorkingOnIt.py''' app from the [[Updating-QML-content-from-Python-threads|Updating <span class="caps">QML</span> content from Python threads]] tutorial.


==Instructions==
[[Category:PySide]]
[[Category:snippets]]
[[Category:Developing_with_Qt::Qt Quick]]
[[Category:Developing_with_Qt::Qt Quick::QML]]
[[Category:Developing_with_Qt::Qt Quick::Tutorial]]


You need to follow the [[Updating-QML-content-from-Python-threads|Updating <span class="caps">QML</span> content from Python threads]] tutorial up to the point where you create the <span class="caps">QML</span> file. As our Python code does not know anything about the <span class="caps">QML</span> internals (it just provides properties and slots for the <span class="caps">QML</span> UI to hook into), we do not need to touch the Python code at all (apart from maybe changing the filename of the <span class="caps">QML</span> file to load in '''setSource''').


===Getting the Colibri library===


You can download the Colibri library from its [https://projects.developer.nokia.com/colibri Nokia Developer project page] ''[projects.developer.nokia.com]''
This [[PySide]] tutorial takes an existing PySide QML application that uses a totally custom UI, and shows how such an UI can be transformed to use a pre-made component library. In the future, it will be useful to use [[Qt Quick Components]], but as it's not ready yet, we are using the open source [https://projects.developer.nokia.com/colibri/ Qt Quick Colibri] library. The existing application that we are modifying for this is the '''WorkingOnIt.py''' app from the [[Updating-QML-content-from-Python-threads|Updating QML content from Python threads ]] tutorial.


Place the folder “colibri” from the sources into the same folder where your '''WorkingOnIt.py''' and '''WorkingOnIt.qml''' files are.
== Instructions ==


===Referencing the library in the <span class="caps">QML</span> file===
You need to follow the [[Updating-QML-content-from-Python-threads|Updating QML content from Python threads ]] tutorial up to the point where you create the QML file. As our Python code does not know anything about the QML internals (it just provides properties and slots for the QML UI to hook into), we do not need to touch the Python code at all (apart from maybe changing the filename of the QML file to load in '''setSource''').


This is pretty straightforward. Add below the “import Qt 4.7” line the following statement:
=== Getting the Colibri library ===


===Reading up on the Colibri documentation===
You can download the Colibri library from its [https://projects.developer.nokia.com/colibri Nokia Developer project page]


Colibri provides [https://projects.developer.nokia.com/colibri/wiki several useful components] ''[projects.developer.nokia.com]'' to work with. In this example, we are using the following components:
Place the folder "colibri" from the sources into the same folder where your '''WorkingOnIt.py''' and '''WorkingOnIt.qml''' files are.


* [https://projects.developer.nokia.com/colibri/wiki/CLButton <span class="caps">CLB</span>utton] ''[projects.developer.nokia.com]''
=== Referencing the library in the QML file ===
* [https://projects.developer.nokia.com/colibri/wiki/CLProgressBar CLProgressBar] ''[projects.developer.nokia.com]''


===Using the components in our <span class="caps">QML</span> file===
This is pretty straightforward. Add below the "import Qt 4.7" line the following statement:


Instead of having the custom progress bar rectangle, we use '''CLProgressBar''' there. It has a “value” property that accepts a value from 0 to 100. Our backend gives us the progress from 0 to 1 as a float, so we simply multiply it by 100 in our UI code.
<code>import "colibri"</code>


Instead of the custom button, we use '''<span class="caps">CLB</span>utton'''. We can take over the “text” property from the old file, and the “onClicked” handler that starts the download can also be copied verbatim from the old example.
=== Reading up on the Colibri documentation ===


As you can see, this allows for a very short <span class="caps">QML</span> file that still looks better than the original, custom UI. You can also replace components part for part, and you can combine widgets from different component libraries.
Colibri provides [https://projects.developer.nokia.com/colibri/wiki several useful components] to work with. In this example, we are using the following components:


==Without Qt Quick Colibri==
* [https://projects.developer.nokia.com/colibri/wiki/CLButton CLButton]
* [https://projects.developer.nokia.com/colibri/wiki/CLProgressBar CLProgressBar]


[[Image:5226958058_6b5b91d1a3.jpg|Without using Colibri]]
=== Using the components in our QML file ===


==With Qt Quick Colibri==
Instead of having the custom progress bar rectangle, we use '''CLProgressBar''' there. It has a "value" property that accepts a value from 0 to 100. Our backend gives us the progress from 0 to 1 as a float, so we simply multiply it by 100 in our UI code.


[[Image:5229084500_da49bab19f.jpg|With using Colibri]]
Instead of the custom button, we use '''CLButton'''. We can take over the "text" property from the old file, and the "onClicked" handler that starts the download can also be copied verbatim from the old example.


==The updated <span class="caps">QML</span> file, utilizing Colibri==
As you can see, this allows for a very short QML file that still looks better than the original, custom UI. You can also replace components part for part, and you can combine widgets from different component libraries.


===Categories:===
== Without Qt Quick Colibri ==


* [[:Category:Developing with Qt|Developing_with_Qt]]
[[Image:Pyswithout.jpg|Without using Colibri]]
** [[:Category:Developing with Qt::Qt-Quick|Qt Quick]]
* [[:Category:Developing with Qt::Qt-Quick::QML|QML]]


* [[:Category:Developing with Qt::Qt-Quick::Tutorial|Tutorial]]
== With Qt Quick Colibri ==


* [[:Category:LanguageBindings|LanguageBindings]]
[[Image:Pyswith.jpg|With using Colibri]]
** [[:Category:LanguageBindings::PySide|PySide]]
 
* [[:Category:snippets|snippets]]
== The updated QML file, utilizing Colibri ==
 
<code>
import Qt 4.7
import "colibri"
 
Rectangle {
width: 200; height: 160
 
Text {
x: progressBar.x; y: 20
width: progressBar.width
font.pixelSize: 8
text: downloader.filename
elide: Text.ElideRight
}
 
CLProgressBar {
id: progressBar
x: 20; y: 60
width: parent.width-40
 
value: downloader.progress*100
}
 
CLButton {
anchors.left: progressBar.left
anchors.right: progressBar.right
 
y: progressBar.y + progressBar.height + 20
 
text: downloader.running?"Please wait…":"Start download"
onClicked: { downloader.start_download() }
}
}
</code>

Latest revision as of 03:32, 5 June 2016



This PySide tutorial takes an existing PySide QML application that uses a totally custom UI, and shows how such an UI can be transformed to use a pre-made component library. In the future, it will be useful to use Qt Quick Components, but as it's not ready yet, we are using the open source Qt Quick Colibri library. The existing application that we are modifying for this is the WorkingOnIt.py app from the Updating QML content from Python threads tutorial.

Instructions

You need to follow the Updating QML content from Python threads tutorial up to the point where you create the QML file. As our Python code does not know anything about the QML internals (it just provides properties and slots for the QML UI to hook into), we do not need to touch the Python code at all (apart from maybe changing the filename of the QML file to load in setSource).

Getting the Colibri library

You can download the Colibri library from its Nokia Developer project page

Place the folder "colibri" from the sources into the same folder where your WorkingOnIt.py and WorkingOnIt.qml files are.

Referencing the library in the QML file

This is pretty straightforward. Add below the "import Qt 4.7" line the following statement:

import "colibri"

Reading up on the Colibri documentation

Colibri provides several useful components to work with. In this example, we are using the following components:

Using the components in our QML file

Instead of having the custom progress bar rectangle, we use CLProgressBar there. It has a "value" property that accepts a value from 0 to 100. Our backend gives us the progress from 0 to 1 as a float, so we simply multiply it by 100 in our UI code.

Instead of the custom button, we use CLButton. We can take over the "text" property from the old file, and the "onClicked" handler that starts the download can also be copied verbatim from the old example.

As you can see, this allows for a very short QML file that still looks better than the original, custom UI. You can also replace components part for part, and you can combine widgets from different component libraries.

Without Qt Quick Colibri

Without using Colibri

With Qt Quick Colibri

With using Colibri

The updated QML file, utilizing Colibri

import Qt 4.7
import "colibri"

Rectangle {
 width: 200; height: 160

Text {
 x: progressBar.x; y: 20
 width: progressBar.width
 font.pixelSize: 8
 text: downloader.filename
 elide: Text.ElideRight
 }

CLProgressBar {
 id: progressBar
 x: 20; y: 60
 width: parent.width-40

value: downloader.progress*100
 }

CLButton {
 anchors.left: progressBar.left
 anchors.right: progressBar.right

y: progressBar.y + progressBar.height + 20

text: downloader.running?"Please wait…":"Start download"
 onClicked: { downloader.start_download() }
 }
}