Qt Creator 2.6.2 has just been released. A quick count yields 55 patches on top of 2.6.1, the majority of them of the Mostly Harmless kind, fixing usability and UI issues. Some serious issues got fixed, too, most notably the code editor freeze some people encountered on certain constructs in the C++ editor (see QTCREATORBUG-8472 and QTCREATORBUG-8532). The full change log is here.
Together with BogDan Vatra, the main author of the Qt for Android port called Necessitas, we have agreed that he will contribute his work into the Qt Project. This is great news and I am truly excited on the things we can do together in the Qt Project. The Qt 5 Android port will be based on the work done in the Necessitas project and BogDan will also continue his work in this area within the Qt Project. This co-operation will enable us to reach Tier 1 status of Qt for Android faster.
Qt for Android is developed actively under the KDE-hosted Necessitas project. There are already many developers who have deployed their apps with it, and an impressive number of users of the Qt-based apps on Android devices – currently over 800.000 active users and 2,7 million downloads. The work done with Qt 4.8 in the Necessitas project provides an excellent baseline to create Qt 5 support together within the Qt Project. Digia is planning to invest into the further development of Qt on Android and aims to introduce Android as fully supported platform of Qt, i.e. as a Tier 1 platform during 2013.
The efforts of getting Qt to run on Android began in late 2010 by BogDan as a hobby project using the newly available QPA of Qt 4.8. The first Alpha release was made available in February 2011 and the port has been steadily growing with supported features, maturity and amount of users. With Qt 5 Android development moving to the Qt Project, the Necessitas project will still continue the work around Qt 4.8. It is expected that the port on Qt 4.8, currently in beta maturity, will be completed in the coming months with most of the work being able to be leveraged on top of Qt 5 in the Qt Project.
It is truly an impressive achievement to create the Android platform support of Qt as well as the Necessitas SDK extending Qt Creator for Android development, and the Ministro installer that allows applications to fetch the needed Qt libraries. BogDan has created most of these, but there have been also many others, for example Ray Donnelly, helping him with the port as well as many others providing feedback.
KDE has been a significant help to the work by providing the needed infrastructure to distribute the SDK as well as the Qt libraries for Android devices. We are grateful for this contribution and hope to be able to continue our co-operation with KDE.
BogDan has expressed interest in being the Qt Project maintainer of the Android port, and I think that would be really great! In addition to BogDan, we want to continue the co-operation with the other members of the community, as we do believe that it is the best way to reach excellent results faster. We are also fully committed in keeping the Android port open and available to all Qt licensees, on both commercial and open-source licenses. The Android port is expected to be available as a development project on top of Qt 5 later this year, and reach full maturity with Qt 5.x releases during next year.
At Qt Developer Days next week in Berlin, we will have a couple of demos running Qt applications on the Android Necessitas port. Hope to see you there. Make sure to sign up! www.qtdeveloperdays.com.
QtQuick 2 promises superior performance, a new particle system and a host of new possibilities:
It is also quite ripe for testing if you are into that kind of thing. This is my personally recommended approach to testing QtQuick 2 on your n9(50) at this point in time and I have to stress that these steps are not officialy sanctioned. I don’t like chroot environments, and since my builds are restricted to Qt which uses the ever rational qmake build system (lone vocal fanboi here) which respects build (qmake profile) sovereignty, I don’t feel I need one. This is an alternate build approach to the webkit team’s approach linked to below and if you would rather follow in the footsteps of wisdom you might want to tail them.
The Webkit team were gracious enough to jot down these instructions:
which I used to setup the sysroot subsequently employed in my mkspec, available here:
This mkspec clearly has to be adjusted to reflect your local dev paths.
0) Realize this is dangerous and might require the reflashing of your device/loss of user data
1) Install the dependencies (as documented in the webkit teams instructions above) in your HARMATTAN_ARMEL target under scratchbox
2) Replace any fully qualified symlinks under $HARMATTAN_ARMEL/usr/lib with relative ones
3) set PKG_CONFIG_SYSROOT_DIR and PKG_CONFIG_PATH in relation to your SYSROOT
4) Run configure directly from qtbase
5) Use the resulting qmake to build the qtdeclarative module
6) Deploy Qt and the required xcb libs to the device (you will need to be root, supplement the existing files don’t override exist files)
You can use:
objdump -x ./plugins/platforms/libxcb.so
to establish what dependencies need to be fulfilled. Up until every required library is present, Qt is gonna tell you that the XCB backend does not exist.
I personally use shadow builds (build out of source) since I am targetting a wide range of devices and discard my builds with fair insane regularity. I have no hit any issues using them in Qt5 when targetting qtbase/qtdeclarative.
Similar steps would clearly probably work for the n900 but, alas, the version of xcb packaged as part of the Fremantle SDK is too old to be used with the XCB QPA backend as it stands. It will take a braver man than me with more time to kill to get that turkey airborne at this point in time. (I also managed to render my Meego 1.2.9 CE unbootable by trying to install the build dependencies, so I don’t see any really convenient avenue for QtQuick 2 experimentation on the n900. Prove me wrong)
Graphic proof of flight, incase you are faring poorly and suspecting that I am a fibber.
The Webkit guys (who tend to have their soup together) have created packages for Qt 5 (along with packing up all the xcb dependencies)
no money back guarantee offered, these packages could quite possibly consume your poodle.
매년 진행되어 온 Qt Developers Days 2011년 행사 소식을 전해 드립니다. 행사 등록 사이트가 정식 오픈 되었습니다. 올해도 참석하시어 Nokia Qt의 새로운 기술 이노베이션을 그 누구보다 더 먼저 선보시길 바랍니다. 올해 행사는 글로벌 행사로써 독일 뮌헨 Munich 10월 24일-26일, 미국 샌프란시스코 San Francisco 11월 29일 – 12월 1일 두 곳에서 진행됩니다. 그리고 12월중에는 중국 베이징 Beijing과 일본 도쿄 Tokyo에서도 각 지역 이벤트가 계획중에 있습니다.
from 2010 Qt Devdays
그리고, Nokia로부터 최근 발표된 뉴스중 Qt와 관련된 중요한 몇 가지 소식을 추려서 말씀 드리겠습니다.
- 최근 Nokia에서는 주요 전략중의 하나의 큰 축인 next billion mobile phones 전략의 Application 플랫폼으로서 Qt를 공식으로 발표하였습니다.
- Nokia는 1년 내에 10개의 새로운 Qt-powered Symbian based device 를 출시할 예정입니다.
- Nokia폰 사용자들은 매일 Ovi Store를 통하여 6백만건의 Application 다운로드를 하고 있습니다. 그 중에는 이미 등록되어 있는 수천개의 Qt application이 포함되어 있고, 그 수는 매우 빠르게 늘고 있습니다. 이러한 사실은 Nokia가 여러분과 같은 Qt개발자에게 제공할 수 잠재적인 가능성을 보여주고 있습니다.
- Nokia N9 – 지금까지 출시된 Qt 탑재 단말에서 가장 인기있는 Linux 기반 터미널 Nokia N9 가 곧 출시됩니다.
Nokia는 Qt의 발전을 위해 많은 기여를 약속(commit)하고 있습니다. 그리고 Qt의 skilled 숙력된 공인 개발자(certified Qt developer)가 되는 것은 현재와 미래를 위해 새로운 기회들을 제공 받는 것입니다.
Qt Developer Days 행사는 Qt가 사용되어 지는 모든 industry에 대한 행사입니다. 그리고 Qt에 대해 배우고, 다른 Qt의 열혈 애호가들을 만날 수 있는 가장 훌륭한 자리 입니다. Qt의 사용은 다른 새로운 industry로 성공적으로 퍼지고 있고, 기존의 다양한 데스크탑이나 임베디드 환경의 프로젝트에서도 성공적인 Qt의 채용이 계속 되고 있습니다.
작년 Qt Developer Days 행사에서도 임베디드 리눅스 환경에서 Qt를 이용한 Adavanced한 GUI 개발에 대한 아주 높은 관심이 있었습니다. 올해 행사에서도 이러한 흐름은 지속될 것입니다. Ubuntu 11.10에 Qt가 정식 채용됨으로써 Qt Developer Days는 Ubuntu의 응용 프로그램이나 장치 UI 개발자뿐만 아니라 다른 Linux 배포판 (단지 하나의 예를 들면, Debian, Fedora, 브라질 Mandriva , openSUSE, 중국의 Red Flag Red Hat, 러시아 ALT 등)에서 Qt를 사용하는 개발자도 흥미로운 이벤트가 될 것입니다.
Qt Developer Days 2011 에서는 다음과 같은 프로그램들이 제공됩니다.
- Qt 전문가들과의 세션 – 숙련된 Qt 개발자들과 Qt 파트너사들과의 시간을 통해 현재 고민하고 있는 Qt 개발 이슈에 대한 답을 찾으실 수 있습니다.
- Qt의 최신 기술을 단시간에 따라잡기위한 Qt Training day
- 50 개 이상의 기술 세션
- Qt 이용 사례 사례 연구 세션
- Qt 파트너와 Qt Ambassador 의한 Qt 어플 리케이션과 Qt 탑재 단말 데모
Director, Qt Ecosystem
It has been a big and busy week already. Last week’s announcement of Symbian Belle and the Nokia 600, Nokia 700 and Nokia 701 was very good news for Qt mobile developers.
Daniel’s blog post on the subject started a lively discussion, and it has been good to see such spirited debate – we want to have conversations with you on this blog, so keep the comments and questions coming.
If last week’s excitement wasn’t enough, today we have more good news. Today we released updates of Qt, the Qt SDK with Qt Simulator, Qt Creator and more (according to our @qtbynokia team, today is “Qt Mega Release Day”).
The detail on each part of today’s release, including links to all of the downloads, is on Qt Labs. Well done and thanks to everyone who contributed to these important releases, and to those who pushed the releases out earlier today.
Finally, a reminder. If you want to talk, learn, or share knowledge with the developers behind these updates and behind Qt programs like Qt 5 and Qt Quick, Qt Developer Days in Munich and San Francisco is the place. Each year the event is the foremost gathering of Qt knowledge, expertise,and community, and it is going to grow in size and diversity again this year.
We have more tech track sessions on desktop and embedded than ever before, smarter scheduling, fantastic keynotes from Canonical, Intel and Telecom Italia (more on this soon) great training training tracks, and a lot more.
Our early bird discount offer is still open, but won’t be open for much longer. If you are thinking about joining us at the event this year, registering now will secure you a spot at the event AND save you money
We’ll have more Qt Developer Days news soon on the Qt blog.
Last week, I went to the MeeGo Conference 2011 in San Francisco, as I said I would the week before. It was a good conference and the organisation is to be congratulated on putting it together (disclaimer: I’m part of said organisation team, even if my contributions were small). The talks were nice, the venue was great, the networking opportunities were invaluable. Yet, when I arrived home on Friday evening, besides feeling very tired, I had the feeling that something was missing. (And I’m writing this blog right now on a plane to Helsinki, an Embraer 190, which makes the Brazilian in me proud; see the proof).
Some people complained about the keynote. I don’t think it was as bad as some people I talked to thought — the SF conference was meant to give a “business spin” to MeeGo, talking about the opportunities going forward, the successes of companies for their using of MeeGo, etc. Yet, I can’t help but agree with the keynote proposal made by Andrew Flegg. I’m wondering if we’ll soon need two conferences: one for the hackers and people working on MeeGo, to plan ahead and celebrate the successes, and another for the business people, device makers, and application developers who are looking at MeeGo as an opportunity.
I think actually that what was missing from this conference was some device announcements. Not device giveaways — no, I think that people who deserve to get hardware will get it anyway at the proper time and, besides, we don’t want to attract “device-leechers” to the conference (that’s a term I heard for the first time in SF, applied to people who go to conferences only to get free devices but don’t have any intention of developing its platform or developing for it). We were missing companies and groups announcing their support for MeeGo, that they are shipping devices that are cool and slick, etc. With those announcements, I think we would get a boost of energy and excitement injected in the community. Those of us working in MeeGo know that, despite the challenges it faces, there’s a lot that you can do already. Rationally, we know that and we have some proof — some products are in the market using MeeGo, like the WeTab and Amino’s set-top-box, but also a lot of lesser known devices. Emotionally, we’d be more excited and committed by seeing and playing with them at the conference.
Another part that will need improvement in the conference is the handling of the Late Breaking News sessions. We need to adjust the number of slots we keep open for late submission, as we had a couple of “holes” in the programme — not a bad thing per se, as we had 6 parallel tracks. On-site scheduling of sessions, especially the BoFs, will need to improve too. We had a few sessions with too few people and some others with too many — we’ll try to adjust for a future conference, but we’ll make mistakes again. I didn’t see any session overcrowded, where no one else could get in and those inside couldn’t breathe.
Of the good things of the conference: the hacker lounge. That was a great idea. It was a great idea in Dublin, with a space for people to just sit back, relax and engage in social activities, like a game of Werewolf. In SF, the organisation took it to the next level, with a great lounge area and free beverages, plus the WiFi connectivity without which no hacker would be happy (I heard connectivity was good, but I don’t have direct evidence since I was using the “meegostaff” AP).
I think we had a compelling line-up of talks too, but I won’t talk too much about this, as it was the Program Committee’s selection and that’s exactly the part of the conference I was directly involved in. In turn, I’ll comment about the talks themselves: I couldn’t watch all of the talks that I wanted to, as I expected to happen. Fortunately, the videos will be posted online soon so I can watch the ones I missed. Of my own talk, I thought I was boring and monotonic — I think I need to repeat those presenter trainings I had 2½ years ago. Thankfully, my poor performance was offset by great performance of the next speaker, Carsten Munk with his talk on transparency, inclusion and meritocracy. Have I mentioned that I used the same three key concepts in my presentation (plus fairness), and we didn’t even sync up?
The Qt 5 and Qt Quick 2.0 talks were very well attended and received. In fact, the presentation of Qt 5 was so well received that the response we got from other MeeGo developers was “that’s great stuff, can we have it sooner?” We had a BoF session to discuss just that and we have a draft plan I should post to the meego-dev mailing list soon. I’m glad I had a part in making sure these talks were present by nudging the presenters, given the number of people who attended them.
Of course, the venue itself was a highlight. The hotel accommodations and the conference area were superb. The conference rooms were large and it was easy to get around. My worry that the escalators from the street level to the second level would be a bottleneck did not come to pass. The sponsors seemed well placed and we had lots of people coming in. At the Qt booth, we were showing the Qt Media Hub and the Chicken Wranglers QML applications.
Unlike Dublin, I didn’t have to spend my time introducing people to other people. I only had to give my business card to one person, and that’s because he had lost the one I had given to him at a previous event. It looks like everyone by now knows each other, which is great. This crowd behaved really well. At the end and on the day after, some came to me and told me they were feeling energised by the event. Instead, I spent my time finding people I needed to talk to and help get problems solved, as well as talking about the Qt Open Governance.
Now, I’m feeling the air pressure in my ears and the pilot is announcing that the we’re initiating the landing procedures (“hyvät matkustajat, tervetuloa Helsinkiin…”). I’ll shut down now and post when I get online.
We powered up our vintage ‘download-o-matic’ mathematical robot this morning and made it crunch some numbers on how many people have downloaded our new SDK.
After several minutes of mechanical chugging and robot sounds it produced a dot matrix printout showing how many people have downloaded the Qt SDK 1.1 since it launched a few weeks ago.
The results (and the robot is never wrong about these things) were pleasing. A large number of people, even larger than we expected, have downloaded the SDK. We also know from talking to developers that lots these downloaders are actively using it.
Now that we know lots of you out there are using the new SDK, we want to hear your thoughts about it. Our motive is simple – if we know more about what you like, what you don’t like, and what you want, it increases our chances of making subsequent releases even better. (more…)
I am very happy to announce the release of a Technology Preview of Qt 4.8 to the community for testing and feedback.
Qt 4.8 will be a release containing a lot of quality and performance improvements that were carried out during the last 12 months, such as File System performance improvements. It also includes the Qt Platform Abstraction (Lighthouse) feature, which enables easier porting of Qt into new graphics systems for third parties. Today’s Technology Preview is released to get your feedback, comments and improvement ideas.
Packages – Qt 4.8 Technology Preview
The Qt 4.8 Tech Preview packages available today have been tested with Windows 7, Mac OS 10.6, Linux and Symbian^3.
Supported platforms for Qt 4.8
Targets for Qt 4.8 will be announced in due course. As a reminder and a guide, the supported platforms for Qt 4.7 are available here http://doc.qt.nokia.com/4.7-snapshot/supported-platforms.html
Deprecated items list in Qt 4.8
As announced recently, we will deprecate a list of items in the Qt 4.8 release. This list can be found in http://labs.qt.nokia.com/2011/05/12/qt-modules-maturity-level-the-list/
We are aiming to release Qt 4.8 beta in next few weeks and the final release candidate in the second half of 2011. These are available through the SDK only.
We would like to thank all developers, contributors, the documentation integration and testing teams in Qt releasing for making this happen!
The Qt 4.8 Tech Preview is available now at
We are looking forward your contributions, comments and suggestions on the Qt 4.8 Tech Preview. Please post your bug reports in http://bugreports.qt.nokia.com.
Pia, on behalf of Qt 4.8 Program Team
Lately I had the chance to research accessibility a bit. Qt supports high contrast color schemes and big fonts as they are set on the platform. Another aspect of accessibility are assistive technologies (AT). That means exposing what an application shows on screen so that an AT-client can interpret it differently. A screen reader can take this information and use speech synthesis to help users navigate the screen. There are several AT standards. The aim for Qt is to support the native interface on all its supported platforms. For Windows at the moment we support MSAA which is a bit dated, but works. For Linux the situation looked rather sad so far. While this is still a research project, the goal is to let Qt and KDE applications be accessible on the Linux desktop.
Lately Orca (the Gnome screen reader) started to work with DBus and AT-SPI 2. With a QAccessibleBridgePlugin Qt can make use of this and provide the same interfaces. The plugin uses Qt’s internal implementation of IAccessible2 (another standard in the jungle of accessibility standards). This is currently work in progress but as you can see in the video, the basics are there.
For applications with custom widgets, the relevant part is to provide a QAccessiblePlugin. This is of course common to all platforms, so you only write it once and for the standard widgets it already comes with Qt.
If you are of the opinion only
seeing hearing is believing, feel free to grab the plugin from gitorious: http://gitorious.org/qt-at-spi.
There is a catch of course: In order to use the plugin you need to have AT-SPI-2 working. Thanks to Mike Gorse and a few others the problems I ran into when testing AT-SPI2 were quickly fixed. The bridge is still
eating kittens making applications crash.
Your have to install at-spi2-core, libatk-adaptor/at-spi2-atk, pyatspi2 and Orca. Accerciser can be a great help for debugging.
Tell gconf to use AT-SPI 2:
gconftool-2 --set /desktop/gnome/interface/at-spi-dbus --type bool true gconftool-2 --set /desktop/gnome/interface/at-spi-corba --type bool false
Set some environment variables:
export GTK_MODULES=gail:atk-bridge export QT_ACCESSIBILITY=1
Thanks to Will and Jonathan we already have some preliminary packages for Suse and Kubuntu. But as said above, it is still in a crashy state. Some fixes made their way into Qt’s master branch already (4.8).
For Qt and KDE applications what is needed now is testing and QAccessiblePlugins for widgets that don’t ship with Qt.
The following post is written by a guest blogger: Digia Plc. Senior Vice President, Mr. Harri Paani
Digia’s plan to acquire the Qt Commercial licensing and service business from Nokia has brought up some justifiable questions about the future of Qt from various stakeholders.
While we understand the need for us to quickly participate the discussion around these matters, we would humbly like to ask for patience from all stakeholders. We can’t participate in the detailed discussions before the transaction is completed.
This is a significant investment for Digia. We want to support the active Qt open source ecosystem and contribute fresh blood to the Qt Commercial licensing and services business. Digia is a software and solutions company, with almost 1 600 top experts worldwide. We are known for our ability to offer our customers clear business benefits as well as our ability to swiftly embrace new technologies, to our customers’ benefit.
Digia has in-depth Qt expertise both from framework development and with demanding projects which makes us a good partner for Qt Commercial customers. Digia is a recognized Qt innovator, delivering the latest Qt technologies into products at the cutting edge of today’s market. Digia has more certified Qt developers than any other company in the industry. (more…)