GUI designing in Qt Creator using the embedded Qt Designer
|Original author(s)||Haavard Nord and Eirik Chambe-Eng|
|Initial release||20 May 1995|
|Stable release||5.8 (January 23, 2017)|
|Operating system||Android, iOS, Linux (Embedded, Wayland, X11), macOS, Windows, Windows Phone, ...|
|License||Qt Commercial License
GPL 2.0, 3.0
Qt ( "cute") is a cross-platform application framework that is used for developing application software that can be run on various software and hardware platforms with little or no change in the underlying codebase, while still being a native application with native capabilities and speed. Qt is currently being developed both by The Qt Company, a company listed on the Nasdaq Helsinki Stock Exchange, and the Qt Project under open-source governance, involving individual developers and firms working to advance Qt. Qt is available with both commercial and open sourceGPL 2.0, GPL 3.0, and LGPL 3.0 licenses.
Qt is used for developing multi-platform applications and graphical user interfaces (GUIs); however, programs without a GUI can be developed, such as command-line tools and consoles for servers. An example of a non-GUI program using Qt is the Cutelyst web framework. GUI programs created with Qt can have a native-looking interface, in which case Qt is classified as a widget toolkit.
Qt is widely used by many organizations, including but not limited to European Space Agency,DreamWorks,Lucasfilm,Panasonic,Philips,Samsung,Siemens,Volvo,Walt Disney Animation Studios,Blizzard Entertainment,Electronic Arts,AMD, Valve Corporation.
Several GUIs and desktop environments utilize Qt as widget toolkit.
Notable applications using Qt or QML are:
Qt, when it was first released, relied on a few key concepts:
Qt works on many different platforms; the following are officially supported:
|X11||Qt for X Window System (Linux, *BSD, HP-UX, Solaris, AIX, etc.)|
|Wayland||Qt for Wayland. Qt applications can switch between graphical backends like X and Wayland at load time with the -platform command line option. This allows a seamless transition of Qt applications from X11 to Wayland.|
|Embedded Linux||Qt for embedded platforms: personal digital assistant, smartphone, etc. Exists as multiple platforms depending on display technology. DirectFB, LinuxFB and EGLFS (EGL Full Screen).|
|Android||Qt for Android, formerly known as Necessitas.|
|macOS||Qt for Apple macOS; supports applications on Cocoa|
|iOS||Qt for iOS platforms (iPhone, iPad)|
|Windows||Qt for Microsoft Windows XP, Vista, 7,8 and 10|
|Windows CE||Qt for Windows CE 6 and Windows Embedded Compact 7.|
|Windows RT||Support for WinRT-based Windows 8 apps and Windows Phone 8 With 5.4 minimum supported version: Windows Phone 8.1|
|Other Embedded Platforms|
|Integrity||Qt for Integrity|
|QNX||Qt for QNX|
|VxWorks||Qt for VxWorks.|
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.
There are four editions of Qt available, Community, Indie Mobile, Professional and Enterprise. 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. Charts and Data Visualization, Enterprise Controls, Virtual Keyboard etc. are commercially sold by The Qt Company.
Qt is available under the following free software licenses:GPL 3.0, LGPL 3.0 and LGPL 2.1 (with Qt special exception). Note that some modules are only available under a GPL license, which means that applications which statically link to these modules need to comply with that license.
|Qt Core||The only required Qt module, containing classes used by other modules, including the meta-object system, concurrency and threading, containers, event system, plugins and I/O facilities.|
|Qt GUI||The central GUI module. In Qt 5 this module now depends on OpenGL, but no longer contains any widget classes.|
|Qt Widgets||Contains classes for classic widget based GUI applications and the QSceneGraph classes. Was split off from QtGui in Qt 5.|
|Qt Quick||The module for GUI application written using QML2.|
|Qt Quick Controls||Widget like controls for Qt Quick intended mainly for desktop applications.|
|Qt Quick Layouts||Layouts for arranging items in Qt Quick.|
|Qt Network||Network abstraction layer. Complete with TCP, UDP, HTTP, SSL and since Qt 5.3 SPDY support.|
|Qt Multimedia||Classes for audio, video, radio and camera functionality.|
|Qt Multimedia Widgets||The widgets from Qt Multimedia.|
|Qt SQL||Contains classes for database integration using SQL.|
|Qt WebEngine||A new set of Qt Widget and QML webview APIs based on Chromium.|
|Qt Test||Classes for unit testing Qt applications and libraries.|
|Active Qt||Classes for applications which use ActiveX.|
|Qt Bluetooth||Classes accessing Bluetooth hardware.|
|Qt D-Bus||Classes for IPC using the D-Bus protocol.|
|Qt NFC||Classes accessing NFC hardware. Only officially supported on BlackBerry hardware so far (or N9 in the MeeGo port).|
|Qt OpenGL||Legacy module containing the OpenGL classes from Qt 4. In Qt 5 the similar functionality in Qt GUI is recommended.|
|Qt Location||Classes for accessing GPS and other location services and for mapping and navigation. Split off from the Qt 4 Mobility module of Qt Location. Supported on Android, BlackBerry, iOS, Linux (using GeoClue), Windows and Sailfish OS.|
|Qt Sensors||Classes for accessing various mobile hardware sensors. Used to be part of Qt Mobile in Qt 4. Supported on Android, BlackBerry, iOS, WinRT, Mer and Linux.|
|Qt Serial Port||Classes for access to hardware and virtual serial ports. Supported on Windows, Linux and macOS.|
|Qt WebChannel||Provides access to Qt objects to HTML/Js over WebSockets.|
|Qt WebKit||Qt's WebKit implementation and API.|
|Qt WebKit Widgets||The widget API for Qt WebKit|
|Qt WebSockets||Provides a WebSocket implementation.|
|Qt XML||Legacy module containing classes for SAX and DOM style XML APIs. Replaced with QXmlStreamReader and QXmlStreamWriter classes in Qt Core.|
|Qt XML Patterns||Support for XPath, XQuery, XSLT and XML Schema validation.|
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. Without such a tool, one would have to write different Makefiles for each platform, so it is useful for abstracting away the differences of various 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).
Qt has a range of bindings for various languages, which implement some or all of its feature set.
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 Windows. 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.
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. This license was viewed as not compliant with the open source principle by the Open Source Initiative and 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 only available 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, 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, which guarantees that Qt would fall under a BSD-style license should no free/open source version of Qt be released during 12 months.
At the end of 2001, Trolltech released Qt 3.0, which added support for Mac OS X. 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. 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. 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. 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 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.
Since then it focused on Qt development to turn it 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. The source code was made available over Gitorious, a community oriented git source code repository, to gather an even broader community that is not only using Qt but also helping to improve it.
In February 2011, Nokia announced its decision to drop Symbian technologies and base their future smartphones on the Windows Phone platform instead. 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. In August 2012, Digia announced that it would acquire Qt from Nokia. The Qt team at Digia started their work in September 2012. They released Qt 5.0 within a month and newer versions every 6 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 related to Qt. In May 2016, Digia and Qt have demerged completely into two independent companies.
Framework development of Qt 5 moved to open governance, taking place at qt-project.org. There it is now possible for developers outside Digia to submit patches and have them reviewed.
the whole QGIS code depends on Qt libraries
Qt uses the native graphics APIs of each platform it supports, taking full advantage of system resources and ensuring that applications have native look and feel.
In case of static linking of the library, the application itself may no longer be "work that uses the library" and thus become subject to LGPL. It is recommended to either link dynamically, or provide the application source code to the user under LGPL.
Qt Wiki provides a comprehensive list of English books about Qt.  This is a list of notable books:
Manage research, learning and skills at defaultLogic. Create an account using LinkedIn or facebook to manage and organize your IT knowledge. defaultLogic works like a shopping cart for information -- helping you to save, discuss and share.