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:
Published Wednesday August 6th, 2014 | by Lars Knoll
Over the last years, many changes have been happening in the Qt ecosystem. One of the biggest was the creation of Qt Project where Qt is now being developed as an open source project. The Qt Project was created to provide a space open for all to further develop and foster innovation for the Qt technology.
Qt has always been a commercial product. During the Trolltech days licensing income funded development of the product. While Nokia’s motivations were different, at Digia, our goal is to again make sure that Qt thrives for all industries, all companies, all users no matter what platform. That said, we need to make sure the business of selling Qt as a product is successful in order to fund its future development for the good of everyone in our ecosystem. The importance of Digia’s commercial business for securing the future of Qt cannot be underestimated as it drives Qt’s foundation and everyday operations. A look into the commit statistics shows that around 75% of all code submissions to qt-project.org come from Digia employees. In addition, Digia manages the release process and the CI and testing infrastructure, thus covering more than 85% of the costs of developing Qt. Read more…
As the dog days of summer carry on, we at Digia, Qt are swatting down flies, mosquitoes and bees while we fan ourselves in the unusual summer heat currently striking Scandinavia … in Oslo … at least.
Meanwhile, on a cool note, the Fun Propulsion Labs at Google announced last week that, VoltAir a single and multi-player game built with Qt is available for download via the Google Play Store and as open source software. Coolbeans!
VoltAir was developed to provide an example of a C++ game designed for both Android and Android TV and the folks at Google also tested it on Nexus 5, Nexus 7, Moto X by Motorola, Android TV, and some Samsung devices.
Check Out VoltAir (Courtesy of Google Developers – YouTube)
We are happy to announce the Qt Creator 3.2 beta today. So you can already check out the many improvements we have done for the upcoming 3.2 release, and, not to forget, give us feedback on what we have so far. We mostly concentrated on stability and improvements, so no completely new platform supported this time, sorry . I’ll randomly highlight some of the changes here, but you should probably check out our change log as well for a more thorough overview, and just download the binaries and try it for yourself.
It’s almost a month since we gathered at the Estrel Conference Center to spend two days talking about Qt, where it is and where it’s heading.
The Summit started off with Lars Knoll giving the state of the project speech, which included status updates from various maintainers. The whole opening session can be watched on Youtube. One thing to raise from Lars’ speech is the need to unify Qt, to bring all Qt users closer to each other.
The two days contained over forty sessions on matters ranging from the use of box2d with QML to two sessions on QtCore. You can find many of the session notes from the Summit schedule page. And the more technical topics have threads on the Developer mailing list, which you can find from the list archives (search for threads marked QtCS).
Over 40 sessions in two days
The weather in Berlin was exceptionally hot, bordering on uncomfortable outside. Luckily the conference center had good air conditioning. However during the evening event we could enjoy the warmth outside in the garden. The setting was very good for continuing the discussions that started during the day. The hardiest participants continued their discussion at the hotel lobby bar after the official evening event was closed.
A big part of events like the Contributors’ Summit are the coffee break and corridor discussions that take place in between sessions. The venue provided enough tables and a couple of good corners with benches to spend some time drafting the upcoming session agenda or working on the topics raised in previous sessions.
Coffee break application demo
A big thank you to all the participants and of course to our sponsors!
Qt Enterprise Embedded provides pre-built system images for a range of popular devices, like the Nexus 7 tablets and the BeagleBone Black. With these, you can make your device “boot to Qt” and be up and running with embedded development literally within minutes. But what if you want to try a device that is not among these reference devices of Qt Enterprise Embedded? Until recently, as an evaluator, you were basically out of luck. And even with an Enterprise license, you would have to rebuild the image from scratch for your device, a process that can take some time. Now, with the recent update of Qt Enterprise Embedded, there is another option available. If your device runs a recent version of Android, it is now possible to install the Boot to Qt stack directly into the existing Android system image; in effect taking it over. We call this method Android injection. In this blog post we will show how this process works in practice. We will use a device called the ODROID-U3 as our example.
We released Qt 5.3.1 a week ago and now we’ve updated the Qt Enterprise Embedded offering as well. In addition to the Qt framework upgrade, we have developed a few new interesting features and also updated the tooling and some of the enterprise add-on features. We are especially proud about our new Android injection solution that lets you take the Boot to Qt software stack into a large variety of Android devices with little effort.
With this update we are also introducing the first Qt supported CoM, Computer-on-Module, for embedded Linux as we announce official support and pre-built binaries for Apalis i.MX6 CoM module from our Qt Technology Partner Toradex. Using the Apalis i.MX6 module from Toradex with our pre-built Qt stack, you can reduce the needed HW and SW effort enabling fast and cost-efficient creation of various embedded systems directly leveraging the state-of-the-art features of this powerful combination.
The initial version of the Qt Virtual Keyboard was released earlier this year, and has quickly become a popular value-add component amongst our Qt Enterprise customers. We are continuously developing it and are now releasing version 1.1, which brings support for Chinese input, 5-way navigation, sound feedback and adds new layouts (languages).
With version 1.1 of the Qt Virtual Keyboard, we are happy to announce that we have made it possible to input Chinese characters using pinyin. Needless to say, this has been a highly requested feature, we are happy to have included.
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.