After Qt 5.3′s introduction of QQuickWidget, Qt 5.4 adds QOpenGLWidget, the long-awaited replacement for the legacy QGLWidget. This widget retains the familiar initializeGL/resizeGL/paintGL API, while enabling full interoperability with other widgets in complex user interfaces.
Internally QOpenGLWidget is built on the same technology as QQuickWidget. Unlike QGLWidget, it is not a native window and will not turn any siblings or ancestors into native either. This avoids stacking, clipping, focus and performance issues and is expected to behave identically across all supported platforms.
Qt 5.4 release process is ongoing and we now have the Qt 5.4 Alpha release available. As always, the Alpha is in source code only. Binary installers will be available in a few weeks with the Beta release. Features of Qt 5.4 are now frozen and in the next months the focus is in finalising and polishing functionality. To give an overview what is coming with Qt 5.4, I’ll summarise the highlights of the Qt 5.4 Alpha release.
Originally we thought the title should be Qt Bug Fixing week, but that would have been too simple.
Here at Digia, we always work to deliver the best Qt releases that we can. We work to fix as many bugs as possible, while still progressing and implementing new features. We try to please everyone and get the balance right.
However, sometimes it’s important to focus. For the week of the 15th to the 22nd of September, we decided we’ll step away from other tasks and take a fresh look at some outstanding issues. We will focus on three areas:
Qt has a great community that likes to know what’s going on and get involved! Instead of only keeping our efforts behind closed doors, we invite everyone to participate. We will coordinate most of the work through IRC (we’ll start #qt-bugs on freenode) and hope to get many P1s out of the way for Qt 5.4.
Qt has supported static builds for a long time, but iOS made this way of shipping Qt more widespread. To make the discussion about static linking more practical, we will not discuss things abstractly, but we will look at how to compile the Weather Info example application from the Qt Positioning module statically for iOS, and address questions as they come up.
We are happy to announce the release of qbs 1.3.0 today. Qbs, or Qt Build Suite, is a general cross-platform build tool that uses a language similar to QML for project description. Qbs can be used for any software project, whether it is written in Qt or not and it simplifies the build process for developing projects across multiple platforms.
If you haven’t tried it out yet, we strongly encourage you to take it for a spin to see how convenient building with Qbs is! Check out the documentation for more details.
What’s new in qbs 1.3?
For this release, we have concentrated on improving the integration with Qt Creator. The main points are:
Source files can now be added to (and removed from) qbs products via the project tree, just as for qmake projects. Thanks to Thomas Epting for the initiative!
More care is now taken to reload a project only if it is really necessary.
In addition, reloading a project has become somewhat faster, particularly in the case where a project file was changed without introducing any semantic differences (e.g. whitespace changes).
We think that these items, combined with a number of important bugfixes, have improved the user experience of working with qbs in Qt Creator a lot.
What else is worth mentioning?
On the language side, it is now possible to set different profiles for particular products. This is important for projects that need to produce binaries for different architectures.
Also, we have once again reduced the memory footprint significantly.
Published Wednesday August 20th, 2014 | by Lars Knoll
20 years ago, Trolltech, the company that created Qt, was founded. One of its founding principles was to release Qt as free software to the open source community. In the early versions, this was limited to Unix/Linux and the X11 windowing system. Over the years, more and more platforms were included into the open source version of Qt.
At the same time, the licenses under which Qt was available evolved. The Qt 1.x source code was still released under a rather restrictive license. With Qt 2, we moved over to the QPL. Some years later, with Qt 4.0, Qt started to embrace the GPL v2, to remove some license conflicts between GPL-based applications and the QPL.
Trolltech was involved in talks with the Free Software Foundation (FSF) when the GPL v3 was created, and we added this license as an optional license for Qt after it was published by the FSF. Finally, in 2009 Nokia added LGPL v2.1 as a licensing option to Qt.
The spirit of all GNU licenses is about a strong copyleft, giving users rather strong access and rights to the source code of application and libraries. It was always meant to protect the users’ freedom to modify the application and underlying libraries and run the modified application.
Note: With Qt Creator 3.2 we drop support for OS X 10.6 (Snow Leopard). The technical reason for this is that Apple does not support any kind of C++11 on that OS version. Of course that does not affect on which platforms you can run your Qt applications on. But it is not possible to run the Qt Creator 3.2 binaries on 10.6, and it also is not possible to compile Qt Creator 3.2 on 10.6 with the tool chains provided by Apple.
Qt Weekly is back from vacation with a post from a guest blogger (*applause*). In this post, Lorenz Haas tells us how to link Qt classes in custom documentation that is generated by using Doxygen.
By mid-2008, Sebastian Pipping introduced doxygen2qthelp for generating Qt Compressed Help files (*.qch) via Doxygen. Already by the end of the year, it was successfully merged into Doxygen. While 22.214.171.124 still had some mirror problems, version 1.5.8 provided stable and comprehensive support for creating QCH files out of the box. See Sebastian’s announcement as well as David Boddie’s article in Qt Quarterly.
Since then, this feature – I guess – has been used a thousand, a million times. Nowadays, I personally can’t imagine working without it. This is because it integrates perfectly into my favorite IDE – Qt Creator. There I can use my own documentation for context-sensitive help that can be triggered by the F1-shortcut:
The Qt Blog provides you with one area for all Qt development posts from our Qt engineering experts. It includes information on projects in the works, tips and tricks, technical release information and more from our pool of very clever Qt developers.