Sep 232012

Research in Motion is a sort of sanctuary for Qt developers – their new platform allows to reuse existing Symbian IP.

Recently, the company has held a series of shows explaining the new operating system and development methods. In the Americas, a special talk was held for BB Java developers – European developers did not get access to this.

Fortunately, the slides of all the events are now available online. Find out more here:

Aug 132012

Nokia has finally decided to let Qt go, for the better of both. We knew it was going to happen sooner than later. Seen as a “non core” business, it was only a formal announcement that was awaited from Nokia.

qt logo Nokia finally gets rid of Qt, sells it to Digia

Digia will acquire the Qt developer tools business from Nokia, and it will take on product development, as well as the commercial and open source licensing and services business supporting Qt.

While Qt was portrayed as missing “genetic link” between OSes, targeted mainly as the savior of developers who could easily target devices powered by both Symbian OS and MeeGo, Nokia could never fully utilize it’s potential.

But for the developer community, this transition may actually prove to save Qt. While Digia plans to quickly enable Qt on Android, iOS and Windows 8 platforms, Nokia has certainly missed to see the silver lining on the clouds – making Qt as the sole cross-platform development framework.

Tommi Laitinen, SVP of International Products at Digia was quoted saying:

Now is a good time for everyone to revisit their perception of Qt. Digia’s targeted R&D investments will bring back focus on Qt’s desktop and embedded platform support, while widening the support for mobile operating systems.

Though the price of the deal is still unknown, it is rumored that Digia will pay a fraction of the US$150 million Nokia paid to acquire Trolltech, the creators of Qt. Also, about 125 Nokia staff will transfer to Digia as a result, mainly in Norway and Germany.

Jul 302012

Qt is a pretty popular development environment for both Symbian and Android development. Given that an IDE is provided by Nokia, it tends to get used quite a lot – and has just been updated.

The following changes were highlighted in what is openly advertised as a bugfix release:

fix in Qt for text editor font rendering on Mac, which would lead to incomplete rendering updates when not using the standard font
(if you build Qt Creator yourself you’ll want to either use the Qt 4.8 branch or cherry-pick 5ac8e6ef178678f500668d67fe38d149f0821029)
fix for C++ template class completion issues
various other fixes

Hit the URL below to find out more:

Jul 282012

This one is an important heads-up to all those of you who are actively developing software (or porting existing Qt IP) for RIMs BlackBerry 10 or PlayBook platforms.

In one of its ususal emails, RIM has hidden a small announcement about an “update” to the developer tools. Of course, no further info was given on the changes – but, as they are pretty severe, they do warrant attention.

So, please head to the following URL and grab the updates:

P.S. In case you are looking for a change log targeted at native developers – look here

Mar 162012

So far, the Qt for Android project has been little less than a permanent source of delight for Qt programmers frustrated by Nokia’s lack of interest in the future of its platform – Bodgan Vatra, after all, did a superior job with the project so far.

Sadly, it looks like the switch to KDE’s infrastructure has raised major unhappyness with some contributors. The email below is from one contributor, with the italic answers from Bodgan Vatra:

WARNING! This post is a rant, expresses only my own opinion and feelings might be harmed during the course of this reading.


This post is a reaction to a thread on the dev list where Bogdan was lamenting on the lack of commitment to the project.
I found it both laughable and pathetic in the sense that NOTHING is done to make it a project you can be committed to, and I’ll expose, IMHO, why.

Until now I find your remarks very insulting …

1) This is a one man (and a half, sorry Ray), “benevolent despot” kind of project.

I’m not going to accept you to insult Ray ! Ray’s contribution is not half !
Because Ray dedicate his free time to this project, now 4000+ users can use this project on windows and mac ! What have you done for this project ?

Bogdan IS the project. Every single decision is made by him without discussions nor appeal. He has his vision for the project (that I didn’t find, but it could be hidden in one of the zillions places the project is scattered into. More on this later) and I don’t feel like he is open to discuss/challenge this vision.

I’m confused ! First you say that “He has his vision for the project that I didn’t find .. ” then you say “I don’t feel like he is open to discuss/ challenge this vision.” !
If you don’t know my vision, how can you say that I’m not open to discuss it, did we ever discuss it ?

Anyway, my expectations for this project are here:

We (you and me) had a few discussions before, but I don’t remember I have been that close…
We talk about menus and about look&feel plugin, I remember that we had different approaches on this topic, you wanted add android look&feel only to your QML, I didn’t agreed, because I still want to support class widgets.
It means that I’m not open to discuss? Please give me more hints on this matter !
BTW Android 9patch is more complex than the standard, so, you can’t use QML BorderImage (qDrawBorderPixmap) to draw the images !

This is human. AFAIK Bogdan created the project and feels he has all rights on it (which he has), but that prevents real involvement from others.
Fact is, if Bogdan is unavailable, the project just plain stops.

Every community project, is based on meritocracy:
You code/contribute, then you have the right to make decisions !

2) NOTHING is done to make it a community project.

I already ranted about this, but the scattering of the project resources is just plain ridiculous, laughable and a HOWTO not to make a coherent project.
Wiki on sourceforge, 1 mailing list on kde and 1 on google groups, 1 bug tracker on sourceforge and 1 on google code, unclear/hidden master repository, unclear contribution process, which leads me to:

If you search this mailing list you’ll find all the informations you
- regarding HOWTO and other information: The pages was written by Damine Treg, sadly he didn’t had time to continue, so I asked may times for peoples help !
Nobody wanted to do it! I can’t do everything by myself !
- 1 on google groups – this is a high traffic general mailing list used by everybody.
- 1 mailing list on kde – this one is a low traffic mailing list used only by developers, I don’t have time to read all posts on google.
- 1 bug tracker on sourceforge and 1 on google code – it was discuss many times before, ONLY bug tracker on sourceforge should be used.
- unclear/hidden master repository: check
- unclear contribution process, as I already said to you before is not may fault !

3) What the f… does necessitas has to do with KDE?

I only assume Bogdan and Ray are KDE devs and that it is easy for them to host necessitas’s master git and “contribution process” on KDE, but this is VERY wrong from a necessitas perspective. KDE might have its own contribution process but it is irrelevant to us and ridiculous for a necessitas contributor to have to register a kde account to be able to use reviewboard, itself, IMHO, a very obscure and complicated system for code contribution vs. what is existing in github or gitorious.
Obviously, all merge requests in the gitorious clone are ignored.
Pretty please, make gitorious the main repository, use gitorious merge request system and do whatever KDE stuff you fancy do in your own KDE corner.

It has everything to do with KDE! Necessitas *IS* a KDE project !
Again, searching this list will give you enough informations.
I’ll try to summarize: When I released first alpha I had to put Ministro libs somewhere, I used some free servers to put the libs, but it was not a good solution. I dedicated my free time to this project and I didn’t wanted to give also my money, so I had to find a reliable solution, back then Nokia just joined Microsoft, to fight against android, so, I had to join somebody, KDE was the natural choice, we share the same goal:
To keep QT free and powerful.

Regarding contributions: We want to upstream everything, the problems
– Nokia doesn’t accept contributions without accepting and sign their contributors agreement,
– I can’t move the project to (they don’t want it yet because is not finished) so you can’t accept their agreement, when you publish your patch.
– The ONLY solution was to “force” contributors to release their code under BSD or public domain

4) Accept contribution, reject them, discuss them or ask for update, DON’T rewrite them.

Crying for contribution, then taking some parts of a patch to rewrite it you way, mostly incompatible with the original patch, is NOT the way to go to motivate contributors.

Again I find some of your remarks very insulting, I’m not “crying”
for contribution !
I’m happy to have more contributor, but i’m not crying !

Some time is easier/faster to rewrite them, then to reject a patch or to ask for updates ! e.g. the menus patch that you sent [1], it didn’t work at all, but I’ve seen a lot potential, so I decide to make it work [2] !
I *CREDIT YOU FOR YOUR WORK* and I push a working version, so, what was wrong in that ?

Probably you are frustrated because I had to revert your last patch, because it was a fiasco, it made the applications almost unusable, is that my fault ?
Probably it is, because I trust your patch and I didn’t run and check all the tests before push it !
The problem is to run and check all the tests it takes too much (1-3 days).

5) The project is sloooooowwwwww.

Due to 1), 2) and Bogdan’s limited availability, necessitas is slow to progress in its own right. I kind of made my own necessitas fork to move on, and due to 4) it has diverged so much from the main trunk that I’m not sure I’ll bother rebasing.

6) Maybe related to 3), I don’t know if it is necessitas or KDE, but one should definitely learn about the “git rebase” command.

All the merges coming from I don’t know which branches makes the git repository unreadable. The proper way to merge upstream is to rebase and resolve conflicts. Merging upstream is pure lazyness.

WOW you are so good! We didn’t know about “git rebase” command !!!
Of course you forgot to learn that you can’t use “git rebase” command when more than one people is using that branch !
Check for more info on this topic.

Merging with upstream is NOT lazyness, is responsibility !

Bottom line:

Necessitas is NOT a community project.

Unless the issues outlined are addressed, It is pointless to whine about necessitas’ lack of contribution.
I suspect many of the more knowledgeable potential contributors will just take the trunk and adapt it to their needs, without bothering trying to contribute it back. Unless the project becomes more community friendly, I’m open to contribute to a potential fork.


I’m open to discuss what is wrong with my vision !
I’m open to know other people vision, so, please share your vision with us!

Don’t forget that this project is based on meritocracy! Even if you have a vision, remember that you must to code it, not only to discuss it !

To be clear: I’m open to discuss, but I’m not going to “cry” for contributors or to accept contributions with insults in the same box !

In the name of the entire Qt community, we can but urge all partners to find a peaceful common ground – if mediation is needed, the Tamoggemon team would love to come to aid…

Mar 152012

Great news..!! Qt Creator 2.5 beta has been released. The new release is full of fun stuff, which even the Qt team cant cover in one blog post. Winking smile

The main features of the release are

…Qt Creator 2.5 understands more of C++11 e.g. nullptr, constexpr, static_assert, noexcept, inline namespaces, auto, and partially lambda.

…Some of the new C++11 types, such as std::shared_ptr, std::unique_ptr, std::array. In addition pretty printers for std::complex, boost::posix_time::{ptime,time_duration}, boost::gregorian::date are new in Qt Creator 2.5

…a TODO plugin

…A clipboard history, use Ctrl+Shift+V to cycle

…Showing small icons for build errors in the editor margin and updating the line numbers of build errors while editing.

taskicons1 Qt Creator 2.5 beta released

image thumb Qt Creator 2.5 beta released

You can download the Qt creator 2.5 from

Happy developing…!!!

Jan 102012

As a matter of fact, Qt 4 has been moved under open governance by the Qt team. As per their blog

Since we released Qt under open governance on, there was always one piece missing. The Qt 4 repository was so far still handled in the old system. This was done as a simple prioritization, to get the parts of Qt that we considered most relevant for the development community out first.

The main problem has been the additional work required to integrate Qt 4 with the continuous integration (CI) system used on qt-project. Thanks to the efforts of Sergio, Rohan and others this has now been (mostly) solved. We run the full CI setup (that includes both compilation and running the test suite) on both Linux and Mac OS X for Qt 4.8. On Windows we currently only run compile tests, running the automated tests on Windows is coming soon.

You can now find the Qt 4.x repository on codereview. Pushing and reviewing changes works the same way as for Qt 5.

Approvers and Maintainers are the same as for the respective areas in Qt 5, but it should be noted that I don’t expect a lot of further development to happen in Qt 4.8. The focus here should be on bug fixes, and patches should be reviewed with this in mind.

The Qt 4.6 and 4.7 branches are not CI tested, so extreme care should be taken when submitting to these branches, and I’d like to see a review from a Maintainer for any change going in there. Changes in these branches should be limited to security issues and severe bugs that can’t be worked around in user code.

Any pending merge requests in gitorious should be resubmitted through gerrit, as we’ll close merge requests on gitorious and turn the repository there into a readonly copy.


Nothing much to add here…!!

Dec 082011

What happens when a creation is orphaned by it’s creator? A very solid example is given in the following email.

Hello folks,

   I writing this mail to inform you about Necessitas alpha4 release status. When we released alpha 3 we said that will try to release alpha 4 (the last one) till the end of November, but I forgot to mention the most important thing: that we also depend on Nokia to release the sable 4.8, because we can’t guarantee something which is not guaranteed by its creator.

Meanwhile we’ll release new updates for current release which will bring more fixes and improved features. On this occasion I’d like to let you know that I just close the very first (and the oldest) Necessitas issue [1]. It is about virtual keyboard support which I managed to rewrite it and (almost) finish it [2]. There are a few small things which are still missing (I’d like to mention the selection which is not the best in town), but, overall I can say that all Qt users will enjoy a first class experience when it comes to input support. The new implementation will be added to the next update (which will come soon).





Nokia has once again proved that it is utmost wise to drop a technology which the entire developer community thinks to be the missing link. Sad.

Nov 102011

After the forced discontinuation of Carbide, developers are left with no options except for Qt Creator. It has just been updated to version 1.1.4.

The following changes are claimed:

The Qt SDK 1.1.4, now available, brings the SDK build targets to the level of the latest Symbian devices and the Nokia N9. It also introduces right-to-left and pinch area support (Qt 4.7.4 / Qt Quick 1.1) and new NFC (near field communication) and Bluetooth APIs (Qt Mobility 1.2)

With the new Qt SDK 1.1.4, you can take advantage of opportunities with the latest Symbian phones and the Nokia N9. This release includes target updates for:

MeeGo 1.2 Harmattan, now a full release.
Symbian Anna Qt 4.7.4 (with Qt Mobility 1.2.1).
Symbian Belle Qt 4.7.4 (with Qt Mobility 1.2.1), which is included in the online installer only.

Not much to add here…

Nov 092011

Qt labs has released the much awaited Qt SDK v1.1.4.  The update is aimed at bringing the SDK build targets to the level of the latest Symbian devices and the Nokia N9.

This means that you can now start developing apps for these devices using

  • Qt 4.7.4 / Qt Quick 1.1 introducing among other things, right-to-left and pinch area support. These things are also supported by today’s Qt Quick Components 1.1 update.
  • Qt Mobility 1.2 which introduces new NFC (near field communication) and Bluetooth APIs, as well as quality improvements to the existing APIs.

You can get the installer files from

Nov 082011

Qt Quick components can best be described as controls/widgets for QML script – with them, an application can be written without having to create controls on your own.

A developer has now sent out the following announcement to the official Qt on Android list:


For information, I’m working on porting the Qt Quick components to Android, with semperXbmc (
semperxbmc/wiki), an XBMC remote control app designed for symbian, as the test case.

I’m starting to get nice results, as can be seen at

I’m using the symbian code as a base, so the look and feel will obviously be very “symbianesque” at first, but who knows…

I will surely need help on the packaging side, as, so far, I have no idea on how to distribute the import plugins/qml thru apk. Obviously, source code will be available as soon as something “clean” comes up.


An example image is shown below:
qml android Qt Quick components on the way to Android

Stay tuned for further info as we get it!