Qt (software)

KDE's mascot Konqi showing his Qt heart

Graphical user-interfaces and desktop environments that utilize Qt/QML as widget toolkit:

• KDE Plasma, a libre desktop environment for various computing devices[19]
• DDE (Deepin Desktop Environment) of Linux Deepin[20][21]
• UKUI (Ubuntu Kylin User Interface)[22]
• CutefishDE[23]
• LXQt (Lightweight X11 Desktop Environment)
• Lumina, a desktop environment designed for BSD-based TrueOS[24]
• Lomiri (formerly Unity8),[25] a convergent desktop environment started by Canonical, maintained by Ubports[26]
• Maui Shell, a DE that also features their own app suite[27]
• Unity 2D, a desktop shell written in Qt and Qml
• Trinity DE, a continuously developed fork based on KDE3[28]
• SDDM, a display manager that is X11 and Wayland compatible written in QML. (This is a display manager and not a desktop environment.)

• Actively developed or maintained
  • AsteroidOS, an open source operating system designed for smartwatches
  • Avionics, Panasonic's in-flight entertainment system[29][30]
  • Blackberry 10, a touchscreen-based mobile OS by Blackberry Ltd.
  • Sailfish OS, a mobile operating system developed by Jolla
  • Plasma Mobile, a touch-based GUI developed by KDE
  • LuneOS, community-driven successor for Palm/HP webOS
  • Nemo Mobile, based on Mer
  • Lomiri, formerly known as Unity8, a phone UI developed by Ubports, originally by Canonical
  • Tesla Model S in-car UI[31]
  • webOS, a multitask operating system from LG for smart devices like TVs and smartwatches
  • Sky Q, the home entertainment system of Sky plc[32]
• Available, but inactive
  • MeeGo handset & tablet UX
  • Qtopia, a system by Nokia for embedded and mobile devices

Many notable open-source or proprietary cross-platform software are using Qt or QML:

Qt is utilized by a wide range of companies and organizations such as

Qt is built on these key concepts:

Complete abstraction of the GUI

When first released, Qt used its own paint engine and controls, emulating the look of the different platforms it runs on when it drew its widgets. This made the porting work easier because very few classes in Qt really depended on the target platform; however, this occasionally led to slight discrepancies where that emulation was imperfect. Recent versions of Qt use the native style APIs of the different platforms, on platforms that have a native widget set, to query metrics and draw most controls, and do not suffer from such issues as often.[85] On some platforms (such as MeeGo and KDE) Qt is the native API. Some other portable graphical toolkits have made different design decisions; for example, wxWidgets uses the toolkits of the target platform for its implementations.

Signals and slots

A language construct introduced in Qt for communication between objects[86] which makes it easy to implement the observer pattern while avoiding boilerplate code. The concept is that GUI widgets can send signals containing event information which can be received by other controls using special functions known as slots.

Metaobject compiler

The metaobject compiler, termed moc, is a tool that is run on the sources of a Qt program. It interprets certain macros from the C++ code as annotations, and uses them to generate added C++ code with meta information about the classes used in the program. This meta information is used by Qt to provide programming features not available natively in C++: signals and slots, introspection and asynchronous function calls.

Language bindings

Qt can be used in several programming languages other than C++, such as Python, Javascript, C# and Rust[87] via language bindings; many languages have bindings for Qt 5 and bindings for Qt 4.

Starting with Qt 4.0 the framework was split into individual modules.[88][89] With Qt 5.0 the architecture was modularized even further.[90][91] Qt is now split into essential and add-on modules.[92]

There are four editions of Qt available: Community, Indie Mobile, Professional and Enterprise.[93] The Community version is under the open source licenses, while the Indie Mobile, Professional and Enterprise versions, which contain additional functionality and libraries, e.g. Enterprise Controls[93] are commercially sold by The Qt Company.

Qt works on many different platforms; the following are officially supported:

After Nokia opened the Qt source code to the community on Gitorious, various ports appeared. There are also some ports of Qt that may be available, but are not supported anymore. These platforms are listed in List of platforms supported by Qt. See also there for current community support for other lesser known platforms, such as SailfishOS.

Qt is available under the following free software licenses:[13] GPL 2.0, GPL 3.0, LGPL 3.0 and LGPL 2.1 (with Qt special exception).[5][111] Note that some modules are available only under a GPL license, which means that applications which link to these modules need to comply with that license.[112]

In addition, Qt has always been available under a commercial license, like the Qt Commercial License,[4] that allows developing proprietary applications with no restrictions on licensing.

Qt comes with its own set of tools to ease cross-platform development, which can otherwise be cumbersome due to different set of development tools.

Qt Creator is a cross-platform IDE for C++ and QML. Qt Designer's GUI layout/design functionality is integrated into the IDE, although Qt Designer can still be started as a standalone tool.

In addition to Qt Creator, Qt provides qmake, a cross-platform build script generation tool that automates the generation of Makefiles for development projects across different platforms. There are other tools available in Qt, including the Qt Designer interface builder and the Qt Assistant help browser (which are both embedded in Qt Creator), the Qt Linguist translation tool, uic (user interface compiler), and moc (Meta-Object Compiler).

In the summer of 1990, Haavard Nord and Eirik Chambe-Eng (the original developers of Qt and the CEO and President, respectively, of Trolltech) were working together on a database application for ultrasound images written in C++ and running on Mac OS, Unix, and Microsoft Windows.[1][113] They began development of "Qt" in 1991, three years before the company was incorporated as Quasar Technologies, then changed the name to Troll Tech and then to Trolltech.[1]

The toolkit was called Qt because the letter Q looked appealing in Haavard's Emacs typeface, and "t" was inspired by Xt, the X toolkit.[1]

The first two versions of Qt had only two flavors: Qt/X11 for Unix and Qt/Windows for Windows.

On 20 May 1995 Troll Tech publicly released Qt 0.90 for X11/Linux with the source code under the Qt Free Edition License.[114][115][116] This license was viewed as not compliant with the free software definition by Free Software Foundation because, while the source was available, it did not allow the redistribution of modified versions. Trolltech used this license until version 1.45. Controversy erupted around 1998 when it became clear that the K Desktop Environment was going to become one of the leading desktop environments for Linux. As it was based on Qt, many people in the free software movement worried that an essential piece of one of their major operating systems would be proprietary.

The Windows platform was available only under a proprietary license, which meant free/open source applications written in Qt for X11 could not be ported to Windows without purchasing the proprietary edition.

With the release of version 2.0 of the toolkit in mid-1999, the license was changed to the Q Public License (QPL), a free software license, but one regarded by the Free Software Foundation as incompatible with the GPL. Compromises were sought between KDE and Trolltech whereby Qt would not be able to fall under a more restrictive license than the QPL, even if Trolltech was bought out or went bankrupt. This led to the creation of the KDE Free Qt foundation,[117] which guarantees that Qt would fall under a BSD-style license should no free/open source version of Qt be released during 12 months.[118][119]

In 2000, Qt/X11 2.2 was released under the GPL v2,[120] ending all controversy regarding GPL compatibility.

At the end of 2001, Trolltech released Qt 3.0, which added support for Mac OS X (now known as macOS). The Mac OS X support was available only in the proprietary license until June 2003, when Trolltech released Qt 3.2 with Mac OS X support available under the GPL.

In 2002, members of the KDE on Cygwin project began porting the GPL licensed Qt/X11 code base to Windows.[121] This was in response to Trolltech's refusal to license Qt/Windows under the GPL on the grounds that Windows was not a free/open source software platform.[122][123] The project achieved reasonable success although it never reached production quality.

This was resolved when Trolltech released Qt 4.0 also for Windows under the GPL in June 2005.[124] Qt 4 supported the same set of platforms in the free software/open source editions as in the proprietary edition, so it is possible, with Qt 4.0 and later releases, to create GPL-licensed free/open source applications using Qt on all supported platforms. The GPL v3 with special exception[125] was later added as an added licensing option. The GPL exception allows the final application to be licensed under various GPL-incompatible free software/open source licenses such as the Mozilla Public License 1.1.

Nokia acquired Trolltech ASA on 17 June 2008 and changed the name first to Qt Software, then to Qt Development Frameworks.

Nokia focused on turning Qt into the main development platform for its devices, including a port to the Symbian S60 platform. Version 1.0 of the Nokia Qt SDK was released on 23 June 2010.[126] The source code was made available over Gitorious, a community oriented git source code repository, with a goal of creating a broader community using and improving Qt.

On 14 January 2009, Qt version 4.5 added another option, the LGPL,[127] to make Qt more attractive for both non-GPL open source projects and closed applications.[128]

In February 2011, Nokia announced its decision to drop Symbian technologies and base their future smartphones on the Windows Phone platform instead (and since then support for that platform has also been dropped).[129] One month later, Nokia announced the sale of Qt's commercial licensing and professional services to Digia, with the immediate goal of taking Qt support to Android, iOS and Windows 8 platforms, and to continue focusing on desktop and embedded development, although Nokia was to remain the main development force behind the framework at that time.

In March 2011, Nokia sold the commercial licensing part of Qt to Digia, creating Qt Commercial.[130] In August 2012, Digia announced that it would acquire Qt from Nokia.[131] The Qt team at Digia started their work in September 2012.[132] They released Qt 5.0 within a month and newer versions every six months with new features and additional supported platforms.

In September 2014, Digia transferred the Qt business and copyrights to their wholly owned subsidiary, The Qt Company, which owns 25 brands[133] related to Qt. In May 2016, Digia and Qt demerged completely into two independent companies.[134]

Qt 5 was officially released on 19 December 2012. This new version marked a major change in the platform, with hardware-accelerated graphics, QML and JavaScript playing a major role. The traditional C++-only QWidgets continued to be supported, but did not benefit from the performance improvements available through the new architecture.[135] Qt 5 brings significant improvements to the speed and ease of developing user interfaces.[136]

Framework development of Qt 5 moved to open governance at qt-project.org, which made it possible for developers outside Digia to submit patches for review.[137]

Distribution of non-Digia Qt contributors (2013, Week 18)

Aside from The Qt Company, many organizations and individuals using Qt as their development platform participate in the open development of Qt via the Qt Project.[138]

One such Qt contributor is Klarälvdalens Datakonsult AB, a Swedish Qt consulting company.[139] KDAB is involved in many areas, including maintenance of several components.[140][141]

Together with RIM/BlackBerry, KDAB is maintaining the QNX and BlackBerry 10 ports of Qt.[138][142]

Another participator is Intel, contributing for example Wayland support.[143] AudioCodes maintains IBM ClearCase support in Qt Creator.[144]

As a heavy user of Qt, the KDE project submits many patches and features from its developer library KDE Frameworks back to Qt.[145]