Thursday I tagged QtWebKit 2.3.2. To avoid confusion I will present both QtWebKit for Qt 5.1 and QtWebKit 2.3.2.

The new features in QtWebKit for Qt 5.1 can be seen on http://qt-project.org/wiki/New-Features-in-Qt-5.1 . Let me expand a few interesting ones below:

Introduction

Coffice (Calligra Office or coffee-in-office) is a new project that tries to make Calligra available on mobile platforms like Android, Blackberry 10, Jolla SailfishOS and Ubuntu Phone.

Good news everybody!

QtWebKit 2.3.0 was tagged in gitorious yesterday with the tarball available there as well

I tagged the first release candidate of QtWebKit 2.3 yesterday. You can find on gitorious, where you also find the tar-ball.

Not much have changed since beta2, crashes fixes, build fixes on non-Linux and a bug that caused browsers to open links in a new window when set to open in new tab.

Just a quick update to tell you beta 2 of QtWebKit 2.3 has been tagged. I am planning to tag the release before the end of the month.

Now that Qt 5.0 has been released, it is time to think about the release of QtWebKit 2.3. For those who do not remember, QtWebKit 2.3 is QtWebKit 3.0 (QtWebKit from Qt 5.0) ported to Qt 4.8.

Beta 1 was tagged yesterday, so go nuts and try it out.

Welcome back, it is has been a long long time since I last made a blog post. Since then I have moved from working on KHTML in my free time to being payed to work on QtWebKit full time. I was hired by Nokia last December and was transferred to Digia in September together with most of the Qt team. At Digia most of our work goes into getting ready for Qt5. We do however have a small side project for Qt 4.x I would like to tell you about, QtWebKit 2.3.

We're hiring Qt developers in Germany, for those who might not know, BlackBerry 10 is using Qt for our core platform with Cascades for our UI/UX framework.

Details are here: https://rim.taleo.net/careersection/professional/jobdetail.ftl?lang=en&job=256223

Short story: Almost 3 years ago Miguel praised elegance of QML compared to XAML. It took so much time to abandon Moonlight but other than technical, the hottest reason is abandoning the XAML/Silverlight and whole .NET-on-Desktops idea by Microsoft itself.

Speaking for myself and not for RIM

With RIM's serious push for Qt as part of the core frameworks and a more Open Source push for its ecosystem, it's the right time for me to jump in.

I Just started my initial porting of the Weather Forecast engine and applet to BlackBerry 10. It won't be Plasma based but pure Qt and Cascades UI with the kinds of effects that I really want to use.

I have to say it's pretty easy to get going. You go here: BlackBerry 10 Development