Simon Hausmann

QtWebKit Releases

Published Wednesday March 3rd, 2010
8 Comments on QtWebKit Releases
Posted in Qt, WebKit

QtWebKit is a part of Qt and we’ve always released them together. With a rapidly growing development community we’d like to decouple QtWebKit from Qt’s releases. It is a project on its own, it’s developed as part of the WebKit project and therefore deserves its own release. We’re going to call the first standalone release simply QtWebKit 2.0.


What does a standalone release mean?

We want to make QtWebKit release available to anyone using Qt, as a source package to install into your existing Qt installation. QtWebKit 2.0 is going to work with Qt 4.6 and 4.7. We will continue to ship QtWebKit in the src/3rdparty/webkit directory in Qt releases, too. It will simply contain the latest stable release. Inside of Qt this will be covered by commercial support.

In the near future we are going to create the release branch and aim for a final 2.0 release in May. I’m going to post future updates about the releasing and branching to our development mailing list

Do you like this? Share it
Share on LinkedInGoogle+Share on FacebookTweet about this on Twitter

Posted in Qt, WebKit


Shyru says:

Great news! Looking forward to replace the qtwebkit (4.6.1) in our application with an updated version.
Any chance Bug 33044 ( being part of this initial release? We would really appreciate Java-support because if qtwebkit still will not have java support, we will have to incorporate IE as rendering engine in our app… πŸ™

girish says:

Makes total sense given that WebKit is moving so fast and a major update to Qt/WebKit happens only when a new minor version of Qt comes out. So, this is really good news, even though it means lot more work for you folks πŸ™‚

Strahinja Markovic says:

Best QtWebKit related news I’ve ever heard. _Brilliant_ idea!

Nitin says:

Does this webkit version support header and footers. I need to print a header and footer while taking printout of some webpage using the webkit. I did not find this yet.

yan says:

But QtScript use webkit JS engine now.
How this decouple will affecte this?

Marius says:

QtScripts JSC engine lives in a separate location in src/3rdpart, and is not affected.

Henry Haverinen says:

I’m also excited about this change!

If you’re a commercial customer and if you’re still wondering about the impacts of this change, let me try to clarify. The first thing to note is that there’s no need to be concerned — you’re free to ignore the whole thing if you like πŸ™‚

As Simon mentioned above, we will continue to include QtWebKit in the Qt framework and Qt SDK releases, so nothing changes there. That will still be the most convenient, out-of-the-box ready way of using QtWebKit. These are the combinations of Qt and QtWebKit for which commercial support is available.

At the moment, the separate QtWebKit source package releases are not going to be productized or supported commercially. They are going to be available for those of you who wish to tap into the latest stuff from WebKit, and who don’t need commercial support for your QtWebKit based project.

lamoscawince says:

Great news!!!

Are these releases work for windows CE too??

Commenting closed.

Get started today with Qt Download now