QML signals to C++? No, the other way around please

While developing an application with QML and C++ please refrain to emit signals in QML that should be handled by C++ code. Just the opposite, keep QML as the UI layer and expose your C++ object to QML (as a context property or with qmlRegisterXXX) and then call a slot or a Q_INVOKABLE method of this object from QML.

QML ListModel is not a QML List Type

As 0 be 1 cannot be (from Star Wars parlance), a QML ListModel is not a list QML Basic Type. Given that said, let's say you have a properly populated ListModel of coordinates (i.e. pairs of latitude and longitude values), and you want to use it as input for a QML MapPolyline to display a polyline in a map...

Using a custom QNetworkAccessManager in QML

The QML Image component has the capability to specify the source of the image is as a URL (using the "source" property) and QML automatically retrieving such image file from a remote location. To do so, QML uses a QNetworkAccessManager (QNAM for short) in the background, which has a lot of default values. But what if you need to set some custom values for the QNAM?

Ever dreamt of creating your own QML controls?

Were you in need of a control not provided in the QML controls set? Have you wondered how difficult could such an enterprise be to write and use your own QML control to fit your needs? Do you feel like contributing any new QML control back to the community?

Qt for Google Native Client

I just found this project by chance, "Qt for Google Native Client" and it seems a very clever idea, opening a lot of possibilities for applications developed with Qt framework. It'll add a new platform for Qt, so confirming once more the "code once, run everywhere" motto.