Qt (software): Difference between revisions

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search
imported>Squizzler
m Add Haiku and Genode operating systems to infobox
 
imported>Coolcoderr
m Removed parentheses
 
(One intermediate revision by one other user not shown)
Line 1: Line 1:
{{Short description|Object-oriented framework for software development}}
{{For|the company formerly known as Qt Software|Qt Group}}
{{For|the company formerly known as Qt Software|Qt Group}}
{{Confuse|QuickTime}}
{{Distinguish|QuickTime}}
 
{{Use dmy dates|date=March 2025}}
{{Use dmy dates|date=March 2025}}
{{Infobox software
{{Infobox software
Line 27: Line 27:
| website = {{URL|https://www.qt.io}}
| website = {{URL|https://www.qt.io}}
}}
}}
{{Short description|Object-oriented framework for software development}}


'''Qt''' ({{IPA|/ˈkjuːt/}} pronounced "cute"<ref>{{cite web|url=https://www.qt.io/about-us/|title=Qt - About Us|archive-url=https://web.archive.org/web/20170222172844/https://www.qt.io/about-us/|archive-date=22 February 2017}}</ref><ref>{{cite web |url=http://bits.blogs.nytimes.com/2010/02/16/that-smartphone-is-so-qt/ |title=That Smartphone Is So Qt |date=16 February 2010 |author=Ashlee Vance |author-link=Ashlee Vance |access-date=19 February 2010 }}</ref>) is a cross-platform application development framework for creating [[graphical user interfaces]] as well as [[Cross-platform software|cross-platform]] applications that run on various software and hardware platforms such as [[Linux]], [[Windows]], [[macOS]], [[Android (operating system)|Android]] or [[embedded system]]s with little or no change in the underlying codebase while still being a native application with native capabilities and speed.
'''Qt''' ({{IPA|/ˈkjuːt/}} pronounced "cute"<ref>{{cite web|url=https://www.qt.io/about-us/|title=Qt - About Us|archive-url=https://web.archive.org/web/20170222172844/https://www.qt.io/about-us/|archive-date=22 February 2017}}</ref><ref>{{cite web |url=http://bits.blogs.nytimes.com/2010/02/16/that-smartphone-is-so-qt/ |title=That Smartphone Is So Qt |date=16 February 2010 |author=Ashlee Vance |author-link=Ashlee Vance |access-date=19 February 2010 }}</ref>) is a cross-platform application development framework for creating [[graphical user interfaces]] as well as [[Cross-platform software|cross-platform]] applications that run on various software and hardware platforms such as [[Linux]], [[Windows]], [[macOS]], [[Android (operating system)|Android]] or [[embedded system]]s with little or no change in the underlying codebase while still being a native application with native capabilities and speed.
Line 48: Line 47:
== Releases ==
== Releases ==


The latest version of the Qt Framework is Qt 6.9, which was released on 2 April 2025.<ref>{{cite web |author1=Volker Hilsheimer |title=Qt 6.9 Released |url=https://www.qt.io/blog/qt-6.9-released |website=www.qt.io |language=en}}</ref>
The latest version of the Qt Framework is Qt 6.10, which was released on 7 October 2025.<ref>{{cite web |author1=Volker Hilsheimer |title=Qt 6.10 Released! |url=https://www.qt.io/blog/qt-6.10-released|date=2025-10-07|website=www.qt.io|language=en|access-date=2025-11-11}}</ref>  


Also still supported are for commercial users — 6.5 LTS, released on 3 April 2023, 6.2 LTS,<ref>{{cite web|url=https://wiki.qt.io/Qt_6.2_Release|title=Qt 6.2.2 Released|date=1 December 2021|website=Qt|publisher=The Qt Company|access-date=6 December 2021}}</ref> released on 30 September 2021, and 5.15 LTS, released on 26 May 2020 – [[long-term support]] (LTS) versions are generally supported for three years with a commercial license, while 5.15 support was extended to five years for subscription license holders, and so it is supported until 26 May 2025. Additionally the [[KDE]] project provides unofficial support for, at least, Qt 5.15, i.e. not just for commercial users.
Also still supported are versions 6.9 until 31 May 2026 and 6.8 LTS until 8 October 2029. Version 6.5 LTS is supported for commercial users only until 30 May 2026. Additionally, extended support for all versions 5.0 (released in 2012) and newer is available for commercial users.<ref name=":0">{{Cite web |title=Qt Releases {{!}} Qt 6.10 |url=https://doc.qt.io/qt-6/qt-releases.html |access-date=2025-11-18 |website=doc.qt.io}}</ref>
 
Minor versions of Qt are typically released twice a year and are supported until one year after release date under standard support conditions. Typically, every third minor version becomes a [[long-term support]] version which gets additional patches. LTS versions are supported for commercial users until five years after their release date (three years prior to version 6.8).<ref name=":0" />


== Qt in use ==
== Qt in use ==
Line 74: Line 75:
* [[KDE Plasma]], a [[libre software|libre]] [[desktop environment]] for various computing devices<ref>{{cite web|url=https://www.kde.org/developerplatform/ |title= The KDE development platform}}</ref>
* [[KDE Plasma]], a [[libre software|libre]] [[desktop environment]] for various computing devices<ref>{{cite web|url=https://www.kde.org/developerplatform/ |title= The KDE development platform}}</ref>
* DDE ([[Deepin]] Desktop Environment) of Linux Deepin<ref>{{cite web |url=http://news.softpedia.com/news/beautifully-crafted-deepin-15-linux-os-gets-a-release-candidate-build-gallery-498074.shtml |title=Beautifully Crafted Deepin 15 Linux OS Drops Ubuntu for Debian Sid, RC Out Now |author=Marius Nestor |date=24 December 2015 |quote=The Deepin desktop environment has been refactored in the latest Qt GUI toolkit, replacing the HTML5 and WebKit frameworks, while Go is still used for the backend.}}</ref><ref>{{cite web|url=https://www.deepin.org/2015/12/23/deepin-15-rc-make-you-only-have-eyes-for-us-by-the-sincerity/|title=深度操作系统 15 RC ——用真心捕获你的芳心 – 深度科技社区|date=23 December 2015|website=Deepin.org|access-date=15 June 2017|archive-date=17 May 2017|archive-url=https://web.archive.org/web/20170517234458/https://www.deepin.org/2015/12/23/deepin-15-rc-make-you-only-have-eyes-for-us-by-the-sincerity/|url-status=dead}}</ref>
* DDE ([[Deepin]] Desktop Environment) of Linux Deepin<ref>{{cite web |url=http://news.softpedia.com/news/beautifully-crafted-deepin-15-linux-os-gets-a-release-candidate-build-gallery-498074.shtml |title=Beautifully Crafted Deepin 15 Linux OS Drops Ubuntu for Debian Sid, RC Out Now |author=Marius Nestor |date=24 December 2015 |quote=The Deepin desktop environment has been refactored in the latest Qt GUI toolkit, replacing the HTML5 and WebKit frameworks, while Go is still used for the backend.}}</ref><ref>{{cite web|url=https://www.deepin.org/2015/12/23/deepin-15-rc-make-you-only-have-eyes-for-us-by-the-sincerity/|title=深度操作系统 15 RC ——用真心捕获你的芳心 – 深度科技社区|date=23 December 2015|website=Deepin.org|access-date=15 June 2017|archive-date=17 May 2017|archive-url=https://web.archive.org/web/20170517234458/https://www.deepin.org/2015/12/23/deepin-15-rc-make-you-only-have-eyes-for-us-by-the-sincerity/|url-status=dead}}</ref>
* UKUI ([[Ubuntu Kylin]] User Interface)<ref>{{cite web|url=https://www.omgubuntu.co.uk/2020/02/ubuntu-kylin-ukui-desktop-qt|title=Wowser, the UKUI 3.0 Desktop Looks Phenomenal (Updated)|author=Joey Sneddon|website=omg!ubuntu!|date=5 February 2020 }}</ref>
* [[UKUI]] ([[Ubuntu Kylin]] User Interface)<ref>{{cite web|url=https://www.omgubuntu.co.uk/2020/02/ubuntu-kylin-ukui-desktop-qt|title=Wowser, the UKUI 3.0 Desktop Looks Phenomenal (Updated)|author=Joey Sneddon|website=omg!ubuntu!|date=5 February 2020 }}</ref>
* CutefishDE, a desktop environment built with Qt Quick and essential KDE frameworks <ref>{{cite web|url=https://www.omgubuntu.co.uk/2021/06/cutefish-new-linux-desktop-environment |title= OMGUbuntu Review|date= 11 June 2021}}</ref>  
* CutefishDE, a desktop environment built with Qt Quick and essential KDE frameworks <ref>{{cite web|url=https://www.omgubuntu.co.uk/2021/06/cutefish-new-linux-desktop-environment |title= OMGUbuntu Review|date= 11 June 2021}}</ref>  
* [[LXQt]] (Lightweight X11 Desktop Environment)
* [[LXQt]] (Lightweight X11 Desktop Environment)
* [[Lumina (desktop environment)|Lumina]], a desktop environment designed for [[BSD]]-based TrueOS<ref>{{cite web|url=http://lumina-desktop.org/ |title= Lumina Homepage}}</ref>
* [[Lumina (desktop environment)|Lumina]], a desktop environment designed for [[BSD]]-based TrueOS<ref>{{cite web|url=http://lumina-desktop.org/ |title= Lumina Homepage}}</ref>
* Lomiri (formerly [[Unity8]]),<ref>{{cite web|url=https://ubports.com/blog/ubports-blog-1/post/lomiri-new-name-same-great-unity8-265|title=Lomiri: New name, Same Great Unity8|website=ubports.com|date=12 July 2019 }}</ref> a convergent desktop environment started by Canonical, maintained by Ubports<ref>{{cite web|url=https://github.com/ubports/unity8/ |title=Unity8 Code Repository on Github|website=Github.com|date=13 September 2022 }}</ref>
* [[Lomiri]] (formerly [[Unity8]]),<ref>{{cite web|url=https://ubports.com/blog/ubports-blog-1/post/lomiri-new-name-same-great-unity8-265|title=Lomiri: New name, Same Great Unity8|website=ubports.com|date=12 July 2019 }}</ref> a convergent desktop environment started by Canonical, maintained by Ubports<ref>{{cite web|url=https://github.com/ubports/unity8/ |title=Unity8 Code Repository on Github|website=Github.com|date=13 September 2022 }}</ref>
* Maui Shell, a DE that also features their own app suite<ref>{{cite web|url=https://www.youtube.com/watch?v=O7gzWHJ_cW4 |title= Review by Tylers Tech channel|website= [[YouTube]]|date= 6 January 2022}}</ref>
* Maui Shell, a DE that also features their own app suite<ref>{{cite web|url=https://www.youtube.com/watch?v=O7gzWHJ_cW4 |title= Review by Tylers Tech channel|website= [[YouTube]]|date= 6 January 2022}}</ref>
* [[Unity (user interface)#Unity 2D|Unity 2D]], a desktop shell written in Qt and Qml
* [[Unity (user interface)#Unity 2D|Unity 2D]], a desktop shell written in Qt and Qml
Line 110: Line 111:
* AMD's [[Radeon Software]] Crimson Edition driver tool application.<ref>{{cite web|url=https://arstechnica.com/gaming/2015/11/amd-radeon-software-crimson-a-new-name-and-a-new-look-for-catalyst/|title=AMD Radeon Software Crimson: A new name and a new look for Catalyst|first=Mark|last=Walton|date=2 November 2015}}</ref>
* AMD's [[Radeon Software]] Crimson Edition driver tool application.<ref>{{cite web|url=https://arstechnica.com/gaming/2015/11/amd-radeon-software-crimson-a-new-name-and-a-new-look-for-catalyst/|title=AMD Radeon Software Crimson: A new name and a new look for Catalyst|first=Mark|last=Walton|date=2 November 2015}}</ref>
* [[Audacious (software)|Audacious]], a music player for [[Linux]], Microsoft Windows, and other [[Unix-like]] operating systems.
* [[Audacious (software)|Audacious]], a music player for [[Linux]], Microsoft Windows, and other [[Unix-like]] operating systems.
* [[Autodesk Fusion 360]]<ref>{{cite web |title="This application failed to start because it could not find or load the Qt platform plug-in" when launching or uninstalling Fusion 360 |url=https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/This-application-failed-to-start-because-it-could-not-find-or-load-the-Qt-platform-plugin-error-when-uninstalling-Fusion-360.html |archive-url=https://web.archive.org/web/20250618094705/https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/This-application-failed-to-start-because-it-could-not-find-or-load-the-Qt-platform-plugin-error-when-uninstalling-Fusion-360.html |archive-date=18 June 2025}}</ref>
* [[Autodesk Maya]]<ref>{{cite web |url=http://qt.nokia.com/qt-in-use/autodesk/ |title=Qt in Autodesk |url-status=dead |archive-url=https://web.archive.org/web/20110723145736/http://qt.nokia.com/qt-in-use/autodesk/ |archive-date=23 July 2011}}</ref>
* [[Autodesk Maya]]<ref>{{cite web |url=http://qt.nokia.com/qt-in-use/autodesk/ |title=Qt in Autodesk |url-status=dead |archive-url=https://web.archive.org/web/20110723145736/http://qt.nokia.com/qt-in-use/autodesk/ |archive-date=23 July 2011}}</ref>
* [[Autodesk 3ds Max]]<ref>{{cite web |url=https://help.autodesk.com/view/3DSMAX/2018/ENU/?guid=__developer_what_s_new_what_s_new_3ds_max_2018_sdk_html |title=What's New: 3ds Max 2018 SDK |website=help.autodesk.com |access-date=14 June 2019 |quote=3ds Max 2018 now uses Qt 5.6.2, and plug-ins can build UIs in Qt using the standard GPL Qt 5.6.2 distribution, and the Visual Studio 2015 Qt add-on}}</ref>
* [[Autodesk 3ds Max]]<ref>{{cite web |url=https://help.autodesk.com/view/3DSMAX/2018/ENU/?guid=__developer_what_s_new_what_s_new_3ds_max_2018_sdk_html |title=What's New: 3ds Max 2018 SDK |website=help.autodesk.com |access-date=14 June 2019 |quote=3ds Max 2018 now uses Qt 5.6.2, and plug-ins can build UIs in Qt using the standard GPL Qt 5.6.2 distribution, and the Visual Studio 2015 Qt add-on}}</ref>
Line 132: Line 134:
* [[LMMS]], a cross-platform music production software
* [[LMMS]], a cross-platform music production software
* [[Mathematica]], a mathematical symbolic computation program, sometimes termed a computer algebra system or program, used in many scientific, engineering, mathematical, and computing fields.<ref>{{cite web |url=http://qt.digia.com/Qt-in-Action/Mathematica-by-Wolfram-Research |title=Mathematica by Wolfram Research |url-status=dead |archive-date=29 May 2013 |archive-url=https://web.archive.org/web/20130529062205/http://qt.digia.com/Qt-in-Action/Mathematica-by-Wolfram-Research}}</ref>
* [[Mathematica]], a mathematical symbolic computation program, sometimes termed a computer algebra system or program, used in many scientific, engineering, mathematical, and computing fields.<ref>{{cite web |url=http://qt.digia.com/Qt-in-Action/Mathematica-by-Wolfram-Research |title=Mathematica by Wolfram Research |url-status=dead |archive-date=29 May 2013 |archive-url=https://web.archive.org/web/20130529062205/http://qt.digia.com/Qt-in-Action/Mathematica-by-Wolfram-Research}}</ref>
* [[Mixxx]], an open-source digital DJ application.<ref>{{cite web |url=https://mixxx.org/get-involved/ |title=Mixxx Get involved}}</ref>
* [[Monero]], a privacy-focused cryptocurrency, implements its official desktop [[Cryptocurrency wallet|wallet software]] using Qt.<ref>{{cite web |title=Monero GUI |url=https://github.com/monero-project/monero-gui |website=[[GitHub]]|date=2 June 2022}}</ref>
* [[Monero]], a privacy-focused cryptocurrency, implements its official desktop [[Cryptocurrency wallet|wallet software]] using Qt.<ref>{{cite web |title=Monero GUI |url=https://github.com/monero-project/monero-gui |website=[[GitHub]]|date=2 June 2022}}</ref>
* [[MuseScore]], an open-source, multiplatform notation software
* [[MuseScore]], an open-source, multiplatform notation software
* [[Open Broadcaster Software|OBS]], a libre cross-platform screencast software
* [[Open Broadcaster Software|OBS]], a libre cross-platform screencast software
* [[Orange (software)|Orange]] data mining suite<ref>{{cite web|url=https://github.com/biolab/orange3|title=Orange3 Data Mining Suite|website=[[GitHub]]|date=3 June 2022 }}</ref>
* [[Orange (software)|Orange]] data mining suite<ref>{{cite web|url=https://github.com/biolab/orange3|title=Orange3 Data Mining Suite|website=[[GitHub]]|date=3 June 2022 }}</ref>
* [[Packet Sender]] Network Test Utility<ref>{{cite web|url=https://github.com/dannagle/PacketSender|title=Packet Sender|website=[[GitHub]]|date=28 September 2025 }}</ref>
* [[ParaView]] open-source cross-platform application for interactive, scientific visualization<ref>{{cite web |url=https://paraview.org|title=Parallel Data Analysis and Visualization Application based on VTK}}</ref>
* [[ParaView]] open-source cross-platform application for interactive, scientific visualization<ref>{{cite web |url=https://paraview.org|title=Parallel Data Analysis and Visualization Application based on VTK}}</ref>
* [[PCSX2]], a free and open-source cross-platform Playstation 2 emulator
* [[PCSX2]], a free and open-source cross-platform PlayStation 2 emulator
* [[qBittorrent]] cross-platform free and open-source BitTorrent client<ref>{{cite web|title=Qbittorrent |url=https://github.com/qbittorrent/qBittorrent |website=[[GitHub]]|date=18 February 2022}}</ref>
* [[qBittorrent]] cross-platform free and open-source BitTorrent client<ref>{{cite web|title=Qbittorrent |url=https://github.com/qbittorrent/qBittorrent |website=[[GitHub]]|date=18 February 2022}}</ref>
* [[QGIS]] geographic information system<ref>{{cite web|url=http://www.qgis.org/pyqgis-cookbook/intro.html |title=PyQGIS Developer Cookbook: Introduction |website=qgis.org |access-date=1 March 2017 |quote=the whole QGIS code depends on Qt libraries}}</ref>
* [[QGIS]] geographic information system<ref>{{cite web |url=http://www.qgis.org/pyqgis-cookbook/intro.html |title=PyQGIS Developer Cookbook: Introduction |url-status=dead |archive-url=https://web.archive.org/web/20170303050906/http://docs.qgis.org/testing/en/docs/pyqgis_developer_cookbook/intro.html |archive-date=3 March 2017 |website=qgis.org |access-date=1 March 2017 |quote=the whole QGIS code depends on Qt libraries }}</ref>
* [[Qtractor]] Audio multitrack recorder and editing software
* [[Qtractor]] Audio multitrack recorder and editing software
* [[QuiteRSS]] Feed Reader
* [[QuiteRSS]] Feed Reader
Line 180: Line 184:
* [[LG]]<ref>{{cite web |first=Jon |last=Porter |url=https://www.theverge.com/2019/6/26/18759414/lg-qt-partnership-webos-cars-automotive-robots-smart-home-devices |title=LG tries to bring webOS to cars, robots, and the smart home with new partnership |date=26 June 2019 |publisher=The Verge |access-date=28 April 2020}}</ref>
* [[LG]]<ref>{{cite web |first=Jon |last=Porter |url=https://www.theverge.com/2019/6/26/18759414/lg-qt-partnership-webos-cars-automotive-robots-smart-home-devices |title=LG tries to bring webOS to cars, robots, and the smart home with new partnership |date=26 June 2019 |publisher=The Verge |access-date=28 April 2020}}</ref>
* [[Lucasfilm]]<ref>{{cite press release |url=https://www.businesswire.com/news/home/20071015006427/en/Lucasfilm-Ltd.-Trolltechs-Qt-Create-User-Interface#.VYJvD2RViko|title=Lucasfilm Entertainment Company Ltd.}}</ref><ref>{{cite web |url=http://qt.nokia.com/qt-in-use/qt-in-visual-effects |title=Qt in Visual Effects |url-status=dead |archive-date=23 July 2011 |archive-url=https://web.archive.org/web/20110723145754/http://qt.nokia.com/qt-in-use/qt-in-visual-effects}}</ref>
* [[Lucasfilm]]<ref>{{cite press release |url=https://www.businesswire.com/news/home/20071015006427/en/Lucasfilm-Ltd.-Trolltechs-Qt-Create-User-Interface#.VYJvD2RViko|title=Lucasfilm Entertainment Company Ltd.}}</ref><ref>{{cite web |url=http://qt.nokia.com/qt-in-use/qt-in-visual-effects |title=Qt in Visual Effects |url-status=dead |archive-date=23 July 2011 |archive-url=https://web.archive.org/web/20110723145754/http://qt.nokia.com/qt-in-use/qt-in-visual-effects}}</ref>
* [[Microsoft]]<ref>{{cite web |url=http://www.qtworldsummit.com/2016/sessions/how-to-transition-your-existing-native-mobile-applications-to-using-a-common-qt-based-core/ | title= Qt World Summit talk}}</ref>
* [[Microsoft]]<ref>{{cite web |url=http://www.qtworldsummit.com/2016/sessions/how-to-transition-your-existing-native-mobile-applications-to-using-a-common-qt-based-core/ |url-status=dead |archive-url=https://web.archive.org/web/20180723122744/http://www.qtworldsummit.com/2016/sessions/how-to-transition-your-existing-native-mobile-applications-to-using-a-common-qt-based-core/ |archive-date=23 July 2018 |title=How to transition your existing, native mobile applications to using a common, Qt-based core}}</ref>
* [[Panasonic]]<ref>{{cite web |url=http://qt.nokia.com/about/news/panasonic-selects-qt-for-hd-video-system |title=Panasonic selects Qt for HD video system |url-status=dead |archive-url=https://web.archive.org/web/20110723145947/http://qt.nokia.com/about/news/panasonic-selects-qt-for-hd-video-system |archive-date=23 July 2011 }}</ref>
* [[Panasonic]]<ref>{{cite web |url=http://qt.nokia.com/about/news/panasonic-selects-qt-for-hd-video-system |title=Panasonic selects Qt for HD video system |url-status=dead |archive-url=https://web.archive.org/web/20110723145947/http://qt.nokia.com/about/news/panasonic-selects-qt-for-hd-video-system |archive-date=23 July 2011 }}</ref>
* [[Philips]]<ref>{{cite web |url=http://qt.nokia.com/qt-in-use/qt-in-ip-communications |title=Qt in IP Communications |url-status=dead |archive-url=https://web.archive.org/web/20110723145930/http://qt.nokia.com/qt-in-use/qt-in-ip-communications |archive-date=23 July 2011 }}</ref>
* [[Philips]]<ref>{{cite web |url=http://qt.nokia.com/qt-in-use/qt-in-ip-communications |title=Qt in IP Communications |url-status=dead |archive-url=https://web.archive.org/web/20110723145930/http://qt.nokia.com/qt-in-use/qt-in-ip-communications |archive-date=23 July 2011 }}</ref>
Line 187: Line 191:
* [[Siemens]]<ref>{{cite web |url=http://qt.nokia.com/qt-in-use/story/customer/siemens |title=Qt helped Siemens deliver a C++ development platform for manufacturing software GUIs |url-status=dead |archive-url=https://web.archive.org/web/20110714191438/http://qt.nokia.com/qt-in-use/story/customer/siemens |archive-date=14 July 2011 }}</ref>
* [[Siemens]]<ref>{{cite web |url=http://qt.nokia.com/qt-in-use/story/customer/siemens |title=Qt helped Siemens deliver a C++ development platform for manufacturing software GUIs |url-status=dead |archive-url=https://web.archive.org/web/20110714191438/http://qt.nokia.com/qt-in-use/story/customer/siemens |archive-date=14 July 2011 }}</ref>
* [[Tesla, Inc.|Tesla]]<ref>{{cite web |url=https://electrek.co/2018/05/19/tesla-releases-softwar-open-source-licences/ |title=Tesla releases some of its software to comply with open source licences |author=Fred Lambert |authorlink=Fred Lambert |date=19 May 2018}}</ref>
* [[Tesla, Inc.|Tesla]]<ref>{{cite web |url=https://electrek.co/2018/05/19/tesla-releases-softwar-open-source-licences/ |title=Tesla releases some of its software to comply with open source licences |author=Fred Lambert |authorlink=Fred Lambert |date=19 May 2018}}</ref>
* [[Tomtom]]<ref>{{cite web |url=https://resources.qt.io/customer-stories-automotive/qt-testimonial-tomtom-hmi-fabrizio-monaco |title=TomTom Builds Automotive HMIs with Qt |access-date=20 May 2019 }}</ref>
* [[Tomtom]]<ref>{{cite web |url=https://resources.qt.io/customer-stories-automotive/qt-testimonial-tomtom-hmi-fabrizio-monaco |title=TomTom Builds Automotive HMIs with Qt |access-date=20 May 2019 |archive-date=28 January 2020 |archive-url=https://web.archive.org/web/20200128023724/https://resources.qt.io/customer-stories-automotive/qt-testimonial-tomtom-hmi-fabrizio-monaco |url-status=dead }}</ref>
* [[Valve Corporation|Valve]]<ref>{{cite web |url=https://developer.valvesoftware.com/wiki/Qt |title=Qt |website=Valve Developer Community |access-date=28 April 2017}}</ref>
* [[Valve Corporation|Valve]]<ref>{{cite web |url=https://developer.valvesoftware.com/wiki/Qt |title=Qt |website=Valve Developer Community |access-date=28 April 2017}}</ref>
* [[Volvo]]<ref>{{cite web|url=http://qt.nokia.com/qt-in-use/story/customer/volvo-mobility-systems |title=Volvo Mobility Systems |archive-url=https://web.archive.org/web/20110714191457/http://qt.nokia.com/qt-in-use/story/customer/volvo-mobility-systems |archive-date=14 July 2011 }}</ref>
* [[Volvo]]<ref>{{cite web|url=http://qt.nokia.com/qt-in-use/story/customer/volvo-mobility-systems |title=Volvo Mobility Systems |archive-url=https://web.archive.org/web/20110714191457/http://qt.nokia.com/qt-in-use/story/customer/volvo-mobility-systems |archive-date=14 July 2011 }}</ref>
Line 198: Line 202:
=== Qt concepts ===
=== Qt concepts ===
Qt is built on these key concepts:
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.<ref>{{cite web|url=http://qt.digia.com/Product/Qt-Core-Features--Functions/Library/|title=Library|quote=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.|publisher=Digia|url-status=dead|archive-url=https://web.archive.org/web/20131101011752/http://qt.digia.com/Product/Qt-Core-Features--Functions/Library/|archive-date=1 November 2013}}</ref> 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<ref>{{cite web|url=https://doc.qt.io/qt-5/signalsandslots.html |title=Signals & Slots - QtCore 5.1 |publisher=Qt Project |date=4 July 2013|access-date=10 April 2015}}</ref> which makes it easy to implement the [[observer pattern]] while avoiding [[boilerplate code]]. The concept is that GUI [[GUI widget|widgets]] can send signals containing event information which can be received by other controls using special functions known as slots.
====Complete abstraction of the GUI====
;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 [[Automatic programming|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, [[Type introspection|introspection]] and asynchronous function calls.
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.<ref>{{cite web|url=http://qt.digia.com/Product/Qt-Core-Features--Functions/Library/|title=Library|quote=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.|publisher=Digia|url-status=dead|archive-url=https://web.archive.org/web/20131101011752/http://qt.digia.com/Product/Qt-Core-Features--Functions/Library/|archive-date=1 November 2013}}</ref> 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.
;Language bindings:Qt can be used in several [[programming language]]s other than C++, such as Python, Javascript, C# and Rust<ref>
 
====Signals and slots====
[[Signals and slots]] are a language construct introduced in Qt for communication between objects<ref>{{cite web|url=https://doc.qt.io/qt-5/signalsandslots.html |title=Signals & Slots - QtCore 5.1 |publisher=Qt Project |date=4 July 2013|access-date=10 April 2015}}</ref> which makes it easy to implement the [[observer pattern]] while avoiding [[boilerplate code]]. The concept is that GUI [[GUI widget|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 [[Automatic programming|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, [[Type introspection|introspection]] and asynchronous function calls.
 
Qt moc does not recognise [[Modules (C++)|modules]] in its preprocessor currently.<ref>{{cite web|url=https://arewemodulesyet.org/tools/|title=Are We Modules Yet?: Tools Support|publisher=Elias Steurer|website=arewemodulesyet.org}}</ref>
 
====Language bindings====
Qt can be used in several [[programming language]]s other than C++, such as Python, JavaScript, C# and Rust<ref>
{{cite web|url=https://www.vandenoever.info/blog/2018/10/30/building_qt_apps_with_cargo.html|title=Qt applications with Cargo|date=30 October 2018|website=www.vandenoever.info|access-date=25 April 2019}}</ref> via [[language binding]]s; many languages have [[list of language bindings for Qt 5|bindings for Qt 5]] and [[list of language bindings for Qt 4|bindings for Qt 4]].
{{cite web|url=https://www.vandenoever.info/blog/2018/10/30/building_qt_apps_with_cargo.html|title=Qt applications with Cargo|date=30 October 2018|website=www.vandenoever.info|access-date=25 April 2019}}</ref> via [[language binding]]s; many languages have [[list of language bindings for Qt 5|bindings for Qt 5]] and [[list of language bindings for Qt 4|bindings for Qt 4]].


=== Qt modules ===
=== Qt modules ===
Starting with Qt 4.0 the framework was split into individual modules.<ref>{{cite web|url=https://dot.kde.org/2005/06/28/trolltech-releases-qt-40|title=Trolltech Releases Qt 4.0|publisher=[[KDE]]|date=28 June 2005|access-date=5 August 2013}}</ref><ref>{{cite web |url=https://qt-project.org/doc/qt-4.8/modules.html |title=All Modules &#124; Documentation |publisher=[[Qt Project]] |access-date=8 April 2013 |archive-url=https://web.archive.org/web/20130329130752/http://qt-project.org/doc/qt-4.8/modules.html |archive-date=29 March 2013 |url-status=dead }}</ref> With Qt 5.0 the architecture was modularized even further.<ref>{{cite web|author=Qt Blog |url=https://blog.qt.io/blog/2012/12/19/qt-5-0/ |title=Introducing Qt 5.0 &#124; Qt Blog |publisher=Digia |date=19 December 2012 |access-date=8 April 2013}}</ref><ref>{{cite web|url=https://dot.kde.org/2012/12/24/qt-50-congratulations-qt-project|title=Qt 5.0 - Congratulations to the Qt Project|author=Kyle Morris|publisher=KDE|date=24 December 2012|access-date=5 August 2013}}</ref> Qt is now split into ''essential'' and ''add-on'' modules.<ref>{{cite web|url=https://doc.qt.io/qt-6/qtmodules.html |title=Qt 6 Documentation: All Modules |publisher=Qt Project |access-date=1 December 2022}}</ref>
Starting with Qt 4.0 the framework was split into individual modules.<ref>{{cite web|url=https://dot.kde.org/2005/06/28/trolltech-releases-qt-40|title=Trolltech Releases Qt 4.0|publisher=[[KDE]]|date=28 June 2005|access-date=5 August 2013}}</ref><ref>{{cite web |url=https://qt-project.org/doc/qt-4.8/modules.html |title=All Modules &#124; Documentation |publisher=[[Qt Project]] |access-date=8 April 2013 |archive-url=https://web.archive.org/web/20130329130752/http://qt-project.org/doc/qt-4.8/modules.html |archive-date=29 March 2013 |url-status=dead }}</ref> With Qt 5.0 the architecture was modularized even further.<ref>{{cite web|author=Qt Blog |url=https://blog.qt.io/blog/2012/12/19/qt-5-0/ |title=Introducing Qt 5.0 &#124; Qt Blog |publisher=Digia |date=19 December 2012 |access-date=8 April 2013}}</ref><ref>{{cite web|url=https://dot.kde.org/2012/12/24/qt-50-congratulations-qt-project|title=Qt 5.0 - Congratulations to the Qt Project|author=Kyle Morris|publisher=KDE|date=24 December 2012|access-date=5 August 2013}}</ref> Qt is now split into ''essential'' and ''add-on'' modules.<ref>{{cite web|url=https://doc.qt.io/qt-6/qtmodules.html |title=Qt 6 Documentation: All Modules |publisher=Qt Project |access-date=1 December 2022}}</ref>
Qt classes by default do not reside in any [[namespace]], but all classes are prefixed with the letter {{mono|Q}}. Qt can be configured to be compiled to reside in a user-defined namespace.<ref>{{Cite web|title=Qt In Namespace|url=https://wiki.qt.io/Qt_In_Namespace|access-date=29 October 2025|website=wiki.qt.io|publisher=Qt Wiki}}</ref> Qt is entirely provided through [[header file]]s, and does not currently support [[Modules (C++)|C++ modules]].


==== Qt essentials ====
==== Qt essentials ====
Line 211: Line 227:
|-
|-
!style="width:12em"|Module
!style="width:12em"|Module
!Header
!Description
!Description
|-
|-
| '''Qt Core'''
| '''Qt Core'''
| <code><QtCore></code>
|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.
|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'''
|'''Qt GUI'''
| <code><QtGui></code>
|The central GUI module. In Qt 5 this module now depends on [[OpenGL]], but no longer contains any widget classes.
|The central GUI module. In Qt 5 this module now depends on [[OpenGL]], but no longer contains any widget classes.
|-
|-
|'''Qt Widgets'''
|'''Qt Widgets'''
|<code><QtWidgets></code>
|Contains classes for classic widget based GUI applications and the QSceneGraph classes. Was split off from '''QtGui''' in Qt 5.
|Contains classes for classic widget based GUI applications and the QSceneGraph classes. Was split off from '''QtGui''' in Qt 5.
|-
|-
|'''Qt QML'''
|'''Qt QML'''
| <code><QtQml></code>
|Module for [[QML]] and [[JavaScript]] languages.
|Module for [[QML]] and [[JavaScript]] languages.
|-
|-
|'''Qt Quick'''
|'''Qt Quick'''
| <code><QtQuick></code>
|The module for GUI applications written using QML2.
|The module for GUI applications written using QML2.
|-
|-
|'''Qt Quick Controls'''
|'''Qt Quick Controls'''
| <code><QtQuickControls></code>
|Widget like controls for '''Qt Quick''' intended mainly for desktop applications.
|Widget like controls for '''Qt Quick''' intended mainly for desktop applications.
|-
|-
|'''Qt Quick Layouts'''
|'''Qt Quick Layouts'''
| <code><QtQuickLayouts></code>
|Layouts for arranging items in '''Qt Quick'''.
|Layouts for arranging items in '''Qt Quick'''.
|-
|-
|'''Qt Network'''
|'''Qt Network'''
| <code><QtNetwork></code>
|Network abstraction layer. Complete with support for [[Transmission Control Protocol|TCP]], [[User Datagram Protocol|UDP]], [[HTTP]], [[Transport Layer Security|TLS]], [[Secure Sockets Layer|SSL]] (in Qt 4) and [[SPDY]] (since Qt 5.3).
|Network abstraction layer. Complete with support for [[Transmission Control Protocol|TCP]], [[User Datagram Protocol|UDP]], [[HTTP]], [[Transport Layer Security|TLS]], [[Secure Sockets Layer|SSL]] (in Qt 4) and [[SPDY]] (since Qt 5.3).
|-
|-
|'''Qt Multimedia'''
|'''Qt Multimedia'''
| <code><QtMultimedia></code>
|Classes for audio, video, radio and camera functionality.
|Classes for audio, video, radio and camera functionality.
|-
|-
|'''Qt Multimedia Widgets'''
|'''Qt Multimedia Widgets'''
| <code><QtMultimediaWidgets></code>
|The widgets from '''Qt Multimedia'''.
|The widgets from '''Qt Multimedia'''.
|-
|-
|'''Qt SQL'''
|'''Qt SQL'''
| <code><QtSql></code>
|Contains classes for database integration using [[SQL]].
|Contains classes for database integration using [[SQL]].
|-
|-
|'''Qt WebEngine'''
|'''Qt WebEngine'''
| <code><QtWebEngine></code>
|A new set of Qt Widget and QML webview APIs based on [[Chromium (web browser)|Chromium]].
|A new set of Qt Widget and QML webview APIs based on [[Chromium (web browser)|Chromium]].
|-
|-
|'''Qt Test'''
|'''Qt Test'''
| <code><QtTest></code>
|Classes for unit testing Qt applications and libraries.
|Classes for unit testing Qt applications and libraries.
|}
|}
Line 257: Line 287:
|-
|-
!style="width:12em"|Module
!style="width:12em"|Module
!Header
!Description
!Description
|-
|-
|'''Active Qt'''
|'''Active Qt'''
|<code><QtActive></code>
|Classes for applications which use [[ActiveX]].
|Classes for applications which use [[ActiveX]].
|-
|-
|'''Qt Charts'''
|'''Qt Charts'''
|<code><QtCharts></code>
|Provides functionality and widgets to plot charts of many kinds
|Provides functionality and widgets to plot charts of many kinds
|-
|-
|'''Qt Bluetooth'''
|'''Qt Bluetooth'''
|<code><QtBluetooth></code>
|Classes accessing [[Bluetooth]] hardware.
|Classes accessing [[Bluetooth]] hardware.
|-
|-
|'''Qt D-Bus'''
|'''Qt D-Bus'''
|<code><QtDBus></code>
|Classes for IPC using the [[D-Bus]] protocol.
|Classes for IPC using the [[D-Bus]] protocol.
|-
|-
|'''Qt NFC'''
|'''Qt NFC'''
|<code><QtNfc></code>
|Classes accessing [[near-field communication|NFC]] hardware. Only officially supported on BlackBerry hardware so far (or N9 in the MeeGo port).
|Classes accessing [[near-field communication|NFC]] hardware. Only officially supported on BlackBerry hardware so far (or N9 in the MeeGo port).
|-
|-
|'''Qt OpenGL'''
|'''Qt OpenGL'''
|<code><QtOpenGL></code>
|Legacy module containing the [[OpenGL]] classes from Qt 4. In Qt 5 the similar functionality in '''Qt GUI''' is recommended.
|Legacy module containing the [[OpenGL]] classes from Qt 4. In Qt 5 the similar functionality in '''Qt GUI''' is recommended.
|-
|-
|'''Qt Location'''
|'''Qt Location'''
|<code><QtLocation></code>
|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.
|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 Quick 3D'''
|'''Qt Quick 3D'''
|<code><Qt3D></code>
|Classes for rendering [[3D models]], [[video games]], simulations and [[3D user interaction|3D user interfaces]], with a '''Qt QML''' API, into a mixed 2D and 3D [[scene graph]].
|Classes for rendering [[3D models]], [[video games]], simulations and [[3D user interaction|3D user interfaces]], with a '''Qt QML''' API, into a mixed 2D and 3D [[scene graph]].
|-
|-
|'''[[QtScript|Qt Script]]'''
|'''[[QtScript|Qt Script]]'''
|<code><QtScript></code>
|Legacy module for scripting Qt application using ECMAScript/[[JavaScript]]. In Qt 5, using similar classes in '''Qt QML''' is recommended.
|Legacy module for scripting Qt application using ECMAScript/[[JavaScript]]. In Qt 5, using similar classes in '''Qt QML''' is recommended.
|-
|-
|'''Qt Sensors'''
|'''Qt Sensors'''
|<code><QtSensors></code>
|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.
|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'''
|'''Qt Serial Port'''
|<code><QtSerialPort></code>
|Classes for access to hardware and virtual serial ports. Supported on Windows, Linux and macOS.
|Classes for access to hardware and virtual serial ports. Supported on Windows, Linux and macOS.
|-
|-
|'''Qt WebChannel'''
|'''Qt WebChannel'''
|<code><QtWebChannel></code>
|Provides access to Qt objects to HTML/Js over [[WebSocket]]s.
|Provides access to Qt objects to HTML/Js over [[WebSocket]]s.
|-
|-
|'''Qt WebKit'''
|'''Qt WebKit'''
|<code><QtWebKit></code>
|Qt's [[WebKit]] implementation and API.
|Qt's [[WebKit]] implementation and API.
|-
|-
|'''Qt WebKit Widgets'''
|'''Qt WebKit Widgets'''
|<code><QtWebKitWidgets></code>
|The widget API for '''Qt WebKit'''
|The widget API for '''Qt WebKit'''
|-
|-
|'''Qt WebSockets'''
|'''Qt WebSockets'''
|<code><QtWebSockets></code>
|Provides a [[WebSocket]] implementation.
|Provides a [[WebSocket]] implementation.
|-
|-
|'''Qt XML'''
|'''Qt XML'''
|<code><QtXml></code>
|Legacy module containing classes for [[Simple API for XML|SAX]] and [[Document Object Model|DOM]] style [[XML]] APIs. Replaced with QXmlStreamReader and QXmlStreamWriter classes in '''Qt Core'''.
|Legacy module containing classes for [[Simple API for XML|SAX]] and [[Document Object Model|DOM]] style [[XML]] APIs. Replaced with QXmlStreamReader and QXmlStreamWriter classes in '''Qt Core'''.
|-
|-
|'''Qt XML Patterns'''
|'''Qt XML Patterns'''
|<code><QtXmlPatterns></code>
|Support for [[XPath]], [[XQuery]], [[XSLT]] and [[XML Schema (W3C)|XML Schema]] validation.
|Support for [[XPath]], [[XQuery]], [[XSLT]] and [[XML Schema (W3C)|XML Schema]] validation.
|}
|}
Line 353: Line 401:
|-
|-
|'''Windows'''
|'''Windows'''
|Qt for Microsoft [[Windows 7]],<ref>{{cite web|url=https://wiki.qt.io/Support_for_Windows |title=Qt Wiki&nbsp;– Support for Windows |publisher=[[Qt Project]] |date=11 August 2011 |access-date=11 August 2013}}</ref> [[Windows 8|8]] and [[Windows 10|10]]<ref>{{cite web|url=http://blog.qt.io/blog/2015/04/29/windows-10-support-in-qt/ |title=Windows 10 Support in Qt |publisher=[[The Qt Company]] |date=29 April 2015 |access-date=28 January 2016}}</ref>
|Qt for Microsoft [[Windows 7]], [[Windows 8|8]], [[Windows 10|10]], and [[Windows 11|11]], as well as [[Universal Windows Platform|UWP]] 10<ref>{{Cite web |title=Supported Platforms {{!}} Qt 5.15 |url=https://doc.qt.io/archives/qt-5.15/supported-platforms.html |access-date=2025-07-05 |website=doc.qt.io}}</ref>
|-
|-
|'''Windows RT'''
|'''Windows RT'''
Line 372: Line 420:
|-
|-
|'''QNX'''
|'''QNX'''
|Qt for [[QNX]]<ref>{{cite web |author=Katherine Barrios |url=http://blog.qt.io/blog/2011/11/29/qt-commercial-formally-supports-qnx-2/ |title=Qt Commercial Formally Supports QNX &#124; Qt Blog |date=29 November 2011 |access-date=13 March 2018}}</ref><ref>{{cite web|url=http://doc.qt.io/qt-5/platform-notes-qnx.html|title=Platform and Compiler Notes - QNX {{!}} Qt 5.10}}</ref>
|Qt for [[QNX]]<ref>{{cite web |author=Katherine Barrios |url=http://blog.qt.io/blog/2011/11/29/qt-commercial-formally-supports-qnx-2/ |title=Qt Commercial Formally Supports QNX &#124; Qt Blog |date=29 November 2011 |access-date=13 March 2018}}</ref><ref>{{cite web|url=http://doc.qt.io/qt-5/platform-notes-qnx.html|title=Platform and Compiler Notes - QNX {{!}} Qt 5.10|access-date=13 March 2018|archive-date=14 March 2018|archive-url=https://web.archive.org/web/20180314043353/http://doc.qt.io/qt-5/platform-notes-qnx.html|url-status=dead}}</ref>
|-
|-
|'''VxWorks'''
|'''VxWorks'''
Line 412: Line 460:


=== Early developments ===
=== Early developments ===
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 [[Classic Mac OS|Mac OS]], [[Unix]], and [[Microsoft Windows]].<ref name="oreilly-qt"/><ref>{{cite web|url=http://www.qt.io/qt20/|title=Qt - Qt20|work=Qt}}</ref> 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.<ref name="oreilly-qt" />
In the summer of 1990, Haavard Nord and Eirik Chambe-Eng (the original developers of Qt and the CEO and President, respectively, of The Qt Company) were working together on a database application for ultrasound images written in C++ and running on [[Classic Mac OS|Mac OS]], [[Unix]], and [[Microsoft Windows]].<ref name="oreilly-qt"/><ref>{{cite web|url=http://www.qt.io/qt20/|title=Qt - Qt20|work=Qt}}</ref> 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.<ref name="oreilly-qt" />


The toolkit was called Qt because the letter [[Q]] looked appealing in Haavard's [[Emacs]] typeface, and "t" was inspired by [[X Toolkit Intrinsics|Xt]], the X toolkit.<ref name="oreilly-qt">{{cite book|title=C++ GUI Programming with Qt 4 |last1=Blanchette |first1=Jasmin |last2=Summerfield |first2=Mark |publisher=[[Prentice-Hall]] |chapter=A Brief History of Qt |pages=xv–xvii |edition=1st |date=June 2006 |chapter-url=http://my.safaribooksonline.com/0131872494/pref04 |access-date=5 August 2013|archive-date=23 September 2019|archive-url=https://web.archive.org/web/20190923193951/https://my.safaribooksonline.com/0131872494/pref04}}</ref>
The toolkit was called Qt because the letter [[Q]] looked appealing in Haavard's [[Emacs]] typeface, and "t" was inspired by [[X Toolkit Intrinsics|Xt]], the X toolkit.<ref name="oreilly-qt">{{cite book|title=C++ GUI Programming with Qt 4 |last1=Blanchette |first1=Jasmin |last2=Summerfield |first2=Mark |publisher=[[Prentice-Hall]] |chapter=A Brief History of Qt |pages=xv–xvii |edition=1st |date=June 2006 |chapter-url=http://my.safaribooksonline.com/0131872494/pref04 |access-date=5 August 2013|archive-date=23 September 2019|archive-url=https://web.archive.org/web/20190923193951/https://my.safaribooksonline.com/0131872494/pref04}}</ref>
Line 429: Line 477:
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.
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.<ref>{{cite web |url=http://qtwin.sourceforge.net/qt3-win32/history.php|title=Q../Windows Edition history|date=5 June 2006|archive-url=https://web.archive.org/web/20100731070812/http://qtwin.sourceforge.net/qt3-win32/history.php|archive-date=31 July 2010}}</ref> 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.<ref>[https://marc.info/?l=kde-cygwin&m=104431728920022&w=2 E-mail to the kde-cygwin mailing list] by Chris January, 4 February 2003
In 2002, members of the [[KDE on Cygwin]] project began porting the GPL licensed Qt/X11 code base to Windows.<ref>{{cite web |url=https://qtwin.sourceforge.net/qt3-win32/history.php|title=Q../Windows Edition history|date=5 June 2006|archive-url=https://web.archive.org/web/20100731070812/http://qtwin.sourceforge.net/qt3-win32/history.php|archive-date=31 July 2010}}</ref> 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.<ref>[https://marc.info/?l=kde-cygwin&m=104431728920022&w=2 E-mail to the kde-cygwin mailing list] by Chris January, 4 February 2003
</ref><ref>{{cite web |url=http://www.trolltech.com/developer/faqs/noncomm.html |title=Qt Non-commercial FAQ |publisher=Trolltech |archive-url=https://web.archive.org/web/20031005175911/http://www.trolltech.com/developer/faqs/noncomm.html |archive-date=5 October 2003}}</ref> The project achieved reasonable success although it never reached production quality.
</ref><ref>{{cite web |url=http://www.trolltech.com/developer/faqs/noncomm.html |title=Qt Non-commercial FAQ |publisher=Trolltech |archive-url=https://web.archive.org/web/20031005175911/http://www.trolltech.com/developer/faqs/noncomm.html |archive-date=5 October 2003}}</ref> The project achieved reasonable success although it never reached production quality.


Line 445: Line 493:


=== Merging and demerging with Digia ===
=== Merging and demerging with Digia ===
In March 2011, Nokia sold the commercial licensing part of Qt to Digia, creating Qt Commercial.<ref name="Nokia and Digia">{{cite web |url=https://blog.qt.io/blog/2011/03/07/nokia-and-digia-working-together/ |title=Nokia and Digia working together to grow the Qt community |date=7 March 2011 |access-date=8 July 2011 |first=Sebastian |last=Nystrom}}</ref> In August 2012, Digia announced that it would acquire Qt from Nokia.<ref>{{cite web|author=Digia Plc |url=https://www.digia.com/en/Home/Company/Press/2012/Digia-to-acquire-Qt-from-Nokia/ |title=Digia to acquire Qt from Nokia |publisher=Digia Plc |date=9 August 2012 |access-date=17 October 2014}}</ref> The Qt team at Digia started their work in September 2012.<ref>{{cite web|author=Digia Plc |url=https://www.digia.com/en/Home/Company/Press/2012/Digia-to-acquire-Qt-from-Nokia/ |title=The journey starts today |publisher=Digia Plc |date=18 September 2012 |access-date=17 October 2014}}</ref> They released Qt 5.0 within a month and newer versions every six months with new features and additional supported platforms.
In March 2011, Nokia sold the commercial licensing part of Qt to Digia, creating Qt Commercial.<ref name="Nokia and Digia">{{cite web |url=https://blog.qt.io/blog/2011/03/07/nokia-and-digia-working-together/ |title=Nokia and Digia working together to grow the Qt community |date=7 March 2011 |access-date=8 July 2011 |first=Sebastian |last=Nystrom}}</ref> In August 2012, Digia announced that it would acquire Qt from Nokia.<ref>{{cite web |author=Digia Plc |url=https://www.digia.com/en/Home/Company/Press/2012/Digia-to-acquire-Qt-from-Nokia/ |title=Digia to acquire Qt from Nokia |publisher=Digia Plc |date=9 August 2012 |access-date=17 October 2014 |archive-date=18 October 2014 |archive-url=https://web.archive.org/web/20141018015054/http://www.digia.com/en/Home/Company/Press/2012/Digia-to-acquire-Qt-from-Nokia/ |url-status=dead }}</ref> The Qt team at Digia started their work in September 2012.<ref>{{cite web |author=Digia Plc |url=https://www.digia.com/en/Home/Company/Press/2012/Digia-to-acquire-Qt-from-Nokia/ |title=The journey starts today |publisher=Digia Plc |date=18 September 2012 |access-date=17 October 2014 |archive-date=18 October 2014 |archive-url=https://web.archive.org/web/20141018015054/http://www.digia.com/en/Home/Company/Press/2012/Digia-to-acquire-Qt-from-Nokia/ |url-status=dead }}</ref> 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<ref>{{cite web|url=https://www.tmdn.org/tmview/bookmark?q=anm:%22qt%20company%22|title=TMview search result shown on September 12th, 2016|website=TMDN.org|access-date=15 June 2017}}</ref> related to Qt. In May 2016, Digia and Qt demerged completely into two independent companies.<ref>{{cite web|url=http://www.digia.com/en/actual/news/2016/digia-and-qt-have-demerged-into-two-companies--digias-new-strategys-main-themes-revealed/|title=Digia and Qt have demerged into two companies – Digia's new strategy's main themes revealed|website=Digia|access-date=15 June 2017|archive-date=17 June 2017|archive-url=https://web.archive.org/web/20170617092521/http://www.digia.com/en/actual/news/2016/digia-and-qt-have-demerged-into-two-companies--digias-new-strategys-main-themes-revealed/|url-status=dead}}</ref>
In September 2014, Digia transferred the Qt business and copyrights to their wholly owned subsidiary, The Qt Company, which owns 25 brands<ref>{{cite web|url=https://www.tmdn.org/tmview/bookmark?q=anm:%22qt%20company%22|title=TMview search result shown on September 12th, 2016|website=TMDN.org|access-date=15 June 2017}}</ref> related to Qt. In May 2016, Digia and Qt demerged completely into two independent companies.<ref>{{cite web|url=http://www.digia.com/en/actual/news/2016/digia-and-qt-have-demerged-into-two-companies--digias-new-strategys-main-themes-revealed/|title=Digia and Qt have demerged into two companies – Digia's new strategy's main themes revealed|website=Digia|access-date=15 June 2017|archive-date=17 June 2017|archive-url=https://web.archive.org/web/20170617092521/http://www.digia.com/en/actual/news/2016/digia-and-qt-have-demerged-into-two-companies--digias-new-strategys-main-themes-revealed/|url-status=dead}}</ref>
Line 462: Line 510:
One such Qt contributor is Klarälvdalens Datakonsult AB, a Swedish Qt consulting company.<ref>{{cite web |url=http://www.kdab.com/kdab-contributions-to-qt-5-0-part-1/ |title=contributions to Qt 5.0 (part 1) |publisher=KDAB |date=20 December 2012 |access-date=8 May 2013}}</ref> KDAB is involved in many areas, including maintenance of several components.<ref>{{cite web|url=http://www.kdab.com/kdab-contributions-to-qt-5-0-part-2/ |title=contributions to Qt 5.0 (part 2) |publisher=KDAB |date=21 December 2012 |access-date=8 May 2013}}</ref><ref>{{cite web|url=http://www.kdab.com/maintaining-qt3d/ |title=Maintaining Qt3D |publisher=KDAB |date=21 December 2012 |access-date=8 May 2013}}</ref>
One such Qt contributor is Klarälvdalens Datakonsult AB, a Swedish Qt consulting company.<ref>{{cite web |url=http://www.kdab.com/kdab-contributions-to-qt-5-0-part-1/ |title=contributions to Qt 5.0 (part 1) |publisher=KDAB |date=20 December 2012 |access-date=8 May 2013}}</ref> KDAB is involved in many areas, including maintenance of several components.<ref>{{cite web|url=http://www.kdab.com/kdab-contributions-to-qt-5-0-part-2/ |title=contributions to Qt 5.0 (part 2) |publisher=KDAB |date=21 December 2012 |access-date=8 May 2013}}</ref><ref>{{cite web|url=http://www.kdab.com/maintaining-qt3d/ |title=Maintaining Qt3D |publisher=KDAB |date=21 December 2012 |access-date=8 May 2013}}</ref>


Together with [[BlackBerry (company)|RIM/BlackBerry]], KDAB is maintaining the [[QNX]] and [[BlackBerry 10]] ports of Qt.<ref name="Stats2012" /><ref>{{cite web |url=http://www.kdab.com/qt5-on-the-qnx-operating-system/ |title=Qt5 on the QNX operating system |publisher=KDAB |date=19 April 2012 |access-date=8 May 2013}}</ref>
Together with [[BlackBerry (company)|RIM/BlackBerry]], KDAB is maintaining the [[QNX]] and [[BlackBerry 10]] ports of Qt.<ref name="Stats2012" /><ref>{{cite web |url=http://www.kdab.com/qt5-on-the-qnx-operating-system/ |title=Qt5 on the QNX operating system |publisher=KDAB |date=19 April 2012 |access-date=8 May 2013 |archive-date=19 July 2013 |archive-url=https://web.archive.org/web/20130719064617/http://www.kdab.com/qt5-on-the-qnx-operating-system/ |url-status=dead }}</ref>


Another participator is [[Intel]], contributing for example [[Wayland (display server protocol)|Wayland]] support.<ref>{{cite web|url=https://www.phoronix.com/scan.php?page=news_item&px=ODYyNQ |title=[Phoronix&#93; Qt Is Now Drawing On Wayland |publisher=Phoronix.com |date=21 September 2010 |access-date=8 May 2013}}</ref> [[AudioCodes]]  maintains [[IBM Rational ClearCase|IBM ClearCase]] support in [[Qt Creator]].<ref>{{cite web|url=http://wiki.qt.io/Maintainers |title=Maintainers &#124; Qt Wiki |publisher=Qt Project |date=12 April 2013 |access-date=8 May 2013}}</ref>
Another participator is [[Intel]], contributing for example [[Wayland (display server protocol)|Wayland]] support.<ref>{{cite web|url=https://www.phoronix.com/scan.php?page=news_item&px=ODYyNQ |title=[Phoronix&#93; Qt Is Now Drawing On Wayland |publisher=Phoronix.com |date=21 September 2010 |access-date=8 May 2013}}</ref> [[AudioCodes]]  maintains [[IBM Rational ClearCase|IBM ClearCase]] support in [[Qt Creator]].<ref>{{cite web|url=http://wiki.qt.io/Maintainers |title=Maintainers &#124; Qt Wiki |publisher=Qt Project |date=12 April 2013 |access-date=8 May 2013}}</ref>

Latest revision as of 19:00, 18 November 2025

Template:Short description Script error: No such module "For". Script error: No such module "Distinguish". Template:Use dmy dates Script error: No such module "Infobox".Template:Template otherScript error: No such module "Check for unknown parameters".Template:Main other

Qt (Script error: No such module "IPA". pronounced "cute"[1][2]) is a cross-platform application development framework for creating graphical user interfaces as well as cross-platform applications that run on various software and hardware platforms such as Linux, Windows, macOS, Android or embedded systems 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 by The Qt Company, a publicly listed company, and the Qt Project under open-source governance, involving individual developers and organizations working to advance Qt.[3][4][5] Qt is available under both commercial licenses[6] and open-source[7] GPL 2.0, GPL 3.0, and LGPL 3.0 licenses.[8][9]

Purposes and abilities

Qt is used for developing graphical user interfaces (GUIs) and multi-platform applications that run on all major desktop platforms and mobile or embedded platforms. Most GUI programs created with Qt have a native-looking interface, in which case Qt is classified as a widget toolkit. Non-GUI programs can also be developed, such as command-line tools and consoles for servers. An example of such a non-GUI program using Qt is the Cutelyst web framework.[10]

Qt supports various C++ compilers, including the GCC and Clang C++ compilers and the Visual Studio suite. It supports other languages with bindings or extensions, such as Python via Python bindings[11] and PHP via an extension for PHP5,[12] and has extensive internationalization support. Qt also provides Qt Quick, that includes a declarative scripting language called QML that allows using JavaScript to provide the logic. With Qt Quick, rapid application development for mobile devices became possible, while logic can still be written with native code as well to achieve the best possible performance.

Other features include SQL database access, XML parsing, JSON parsing, thread management and network support.

Releases

The latest version of the Qt Framework is Qt 6.10, which was released on 7 October 2025.[13]

Also still supported are versions 6.9 until 31 May 2026 and 6.8 LTS until 8 October 2029. Version 6.5 LTS is supported for commercial users only until 30 May 2026. Additionally, extended support for all versions 5.0 (released in 2012) and newer is available for commercial users.[14]

Minor versions of Qt are typically released twice a year and are supported until one year after release date under standard support conditions. Typically, every third minor version becomes a long-term support version which gets additional patches. LTS versions are supported for commercial users until five years after their release date (three years prior to version 6.8).[14]

Qt in use

In 2017, the Qt Company estimated a community of about 1 million developers worldwide[15] in over 70 industries.[16]

Desktop UIs

File:KDE Mascot Konqi for Qt.png
KDE's mascot Konqi

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

Embedded and mobile UIs

  • Actively developed or maintained
    • AsteroidOS, an open source operating system designed for smartwatches
    • Avionics, Panasonic's in-flight entertainment system[27][28]
    • 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[29]
    • webOS, a multitask operating system from LG for smart devices like TVs and smartwatches
    • Sky Q, the home entertainment system of Sky plc[30]
  • Available, but inactive
    • MeeGo handset and tablet UX
    • Qtopia, a system by Nokia for embedded and mobile devices

Applications using Qt

Script error: No such module "Labelled list hatnote". Many notable open-source or proprietary cross-platform software are using Qt or QML: Template:Div col

Template:Div col end

Organizations using Qt

Qt is utilized by a wide range of companies and organizations such as Template:Div col

Template:Div col end

Qt software architecture

File:Free and open-source-software display servers and UI toolkits.svg
Example of Qt usage in Linux-based systems

Qt concepts

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.[89] 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

Signals and slots are a language construct introduced in Qt for communication between objects[90] 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.

Qt moc does not recognise modules in its preprocessor currently.[91]

Language bindings

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

Qt modules

Starting with Qt 4.0 the framework was split into individual modules.[93][94] With Qt 5.0 the architecture was modularized even further.[95][96] Qt is now split into essential and add-on modules.[97]

Qt classes by default do not reside in any namespace, but all classes are prefixed with the letter Template:Mono. Qt can be configured to be compiled to reside in a user-defined namespace.[98] Qt is entirely provided through header files, and does not currently support C++ modules.

Qt essentials

Module Header Description
Qt Core <QtCore> 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 <QtGui> The central GUI module. In Qt 5 this module now depends on OpenGL, but no longer contains any widget classes.
Qt Widgets <QtWidgets> Contains classes for classic widget based GUI applications and the QSceneGraph classes. Was split off from QtGui in Qt 5.
Qt QML <QtQml> Module for QML and JavaScript languages.
Qt Quick <QtQuick> The module for GUI applications written using QML2.
Qt Quick Controls <QtQuickControls> Widget like controls for Qt Quick intended mainly for desktop applications.
Qt Quick Layouts <QtQuickLayouts> Layouts for arranging items in Qt Quick.
Qt Network <QtNetwork> Network abstraction layer. Complete with support for TCP, UDP, HTTP, TLS, SSL (in Qt 4) and SPDY (since Qt 5.3).
Qt Multimedia <QtMultimedia> Classes for audio, video, radio and camera functionality.
Qt Multimedia Widgets <QtMultimediaWidgets> The widgets from Qt Multimedia.
Qt SQL <QtSql> Contains classes for database integration using SQL.
Qt WebEngine <QtWebEngine> A new set of Qt Widget and QML webview APIs based on Chromium.
Qt Test <QtTest> Classes for unit testing Qt applications and libraries.

Qt add-ons

Module Header Description
Active Qt <QtActive> Classes for applications which use ActiveX.
Qt Charts <QtCharts> Provides functionality and widgets to plot charts of many kinds
Qt Bluetooth <QtBluetooth> Classes accessing Bluetooth hardware.
Qt D-Bus <QtDBus> Classes for IPC using the D-Bus protocol.
Qt NFC <QtNfc> Classes accessing NFC hardware. Only officially supported on BlackBerry hardware so far (or N9 in the MeeGo port).
Qt OpenGL <QtOpenGL> Legacy module containing the OpenGL classes from Qt 4. In Qt 5 the similar functionality in Qt GUI is recommended.
Qt Location <QtLocation> 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 Quick 3D <Qt3D> Classes for rendering 3D models, video games, simulations and 3D user interfaces, with a Qt QML API, into a mixed 2D and 3D scene graph.
Qt Script <QtScript> Legacy module for scripting Qt application using ECMAScript/JavaScript. In Qt 5, using similar classes in Qt QML is recommended.
Qt Sensors <QtSensors> 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 <QtSerialPort> Classes for access to hardware and virtual serial ports. Supported on Windows, Linux and macOS.
Qt WebChannel <QtWebChannel> Provides access to Qt objects to HTML/Js over WebSockets.
Qt WebKit <QtWebKit> Qt's WebKit implementation and API.
Qt WebKit Widgets <QtWebKitWidgets> The widget API for Qt WebKit
Qt WebSockets <QtWebSockets> Provides a WebSocket implementation.
Qt XML <QtXml> Legacy module containing classes for SAX and DOM style XML APIs. Replaced with QXmlStreamReader and QXmlStreamWriter classes in Qt Core.
Qt XML Patterns <QtXmlPatterns> Support for XPath, XQuery, XSLT and XML Schema validation.

Editions

There are four editions of Qt available: Community, Indie Mobile, Professional and Enterprise.[99] 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[99] are commercially sold by The Qt Company.

Supported platforms

Script error: No such module "Labelled list hatnote".

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

Platform Description
Linux/Unix
X11 Qt for X Window System (Linux);[100] FreeBSD, NetBSD, OpenBSD, and DragonFly BSD have community support.
Wayland Qt applications can switch between graphical backends like X and Wayland at load time with the -platform command line option.[101][102] This allows a seamless transition of Qt applications from X11 to Wayland. SailfishOS uses Wayland only as it does not have X11.[103]
Android Qt for Android[104] (formerly known as Necessitas).[105]
Embedded Linux Qt for embedded platforms: personal digital assistant, smartphone, etc.[106] Exists as multiple platforms depending on display technology. DirectFB, LinuxFB and EGLFS (EGL Full Screen).
Microsoft platforms
Windows Qt for Microsoft Windows 7, 8, 10, and 11, as well as UWP 10[107]
Windows RT Support for WinRT-based Windows 10 Mobile apps and Windows 10 IoT[108]
Apple platforms
macOS Qt for Apple macOS; supports applications on Cocoa[109]
iOS Qt for iOS platforms (iPhone, iPad)[110]
Other embedded platforms
Integrity Qt for Integrity[111]
QNX Qt for QNX[112][113]
VxWorks Qt for VxWorks.[114][115] Only available under a proprietary (commercial) license. Qt 5.5.
QT for MCUs QT for MCUs[116]

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.

Licensing

Qt is available under the following free software licenses:[7] GPL 2.0, GPL 3.0, LGPL 3.0 and LGPL 2.1 (with Qt special exception).[8][117] 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.[118]

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

Qt tools

Script error: No such module "Labelled list hatnote".

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).

History of Qt

Early developments

In the summer of 1990, Haavard Nord and Eirik Chambe-Eng (the original developers of Qt and the CEO and President, respectively, of The Qt Company) were working together on a database application for ultrasound images written in C++ and running on Mac OS, Unix, and Microsoft Windows.[119][120] 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.[119]

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.[119]

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

On 20 May 1995 Trolltech publicly released Qt 0.90 for X11/Linux with the source code under the Qt Free Edition License.[121][122][123] 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.

Becoming free software–friendly

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,[124] which guarantees that Qt would fall under a BSD-style license should no free/open source version of Qt be released during 12 months.[125][126]

In 2000, Qt/X11 2.2 was released under the GPL v2,[127] 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.[128] 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.[129][130] 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.[131] 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[132] 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.

Acquisition by Nokia

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.[133] 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,[134] to make Qt more attractive for both non-GPL open source projects and closed applications.[135]

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).[136] 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.

Merging and demerging with Digia

In March 2011, Nokia sold the commercial licensing part of Qt to Digia, creating Qt Commercial.[137] In August 2012, Digia announced that it would acquire Qt from Nokia.[138] The Qt team at Digia started their work in September 2012.[139] 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[140] related to Qt. In May 2016, Digia and Qt demerged completely into two independent companies.[141]

The Qt Project and open governance

Script error: No such module "Labelled list hatnote".

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.[142] Qt 5 brings significant improvements to the speed and ease of developing user interfaces.[143]

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.[144]

Qt contributors

File:Qt contributors 2013W18 without Digia.png
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.[145]

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

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

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

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

See also

Bibliography

Qt Wiki provides a comprehensive list of English books about Qt.[153] This is a list of notable books:

Template:Refbegin

  • Script error: No such module "citation/CS1".
  • Script error: No such module "citation/CS1".
  • Script error: No such module "citation/CS1".
  • Script error: No such module "citation/CS1".
  • Script error: No such module "citation/CS1".
  • Script error: No such module "citation/CS1".
  • Script error: No such module "citation/CS1".
  • Script error: No such module "citation/CS1".
  • Script error: No such module "citation/CS1".

Template:Refend

References

Template:Reflist

External links

Template:Sister project Template:Sister project

Template:Qt Template:KDE Template:Widget toolkits Template:GUI builders

  1. Script error: No such module "citation/CS1".
  2. Script error: No such module "citation/CS1".
  3. Script error: No such module "citation/CS1".
  4. Script error: No such module "citation/CS1".
  5. Script error: No such module "citation/CS1".
  6. a b Script error: No such module "citation/CS1".
  7. a b Script error: No such module "citation/CS1".
  8. a b Script error: No such module "citation/CS1".
  9. Cite error: Invalid <ref> tag; no text was provided for refs named Adding LGPLv3
  10. Script error: No such module "citation/CS1".
  11. Script error: No such module "citation/CS1".
  12. Script error: No such module "citation/CS1".
  13. Script error: No such module "citation/CS1".
  14. a b Script error: No such module "citation/CS1".
  15. Script error: No such module "citation/CS1".
  16. Script error: No such module "citation/CS1".
  17. Script error: No such module "citation/CS1".
  18. Script error: No such module "citation/CS1".
  19. Script error: No such module "citation/CS1".
  20. Script error: No such module "citation/CS1".
  21. Script error: No such module "citation/CS1".
  22. Script error: No such module "citation/CS1".
  23. Script error: No such module "citation/CS1".
  24. Script error: No such module "citation/CS1".
  25. Script error: No such module "citation/CS1".
  26. Script error: No such module "citation/CS1".
  27. Script error: No such module "citation/CS1".
  28. Script error: No such module "citation/CS1".
  29. Script error: No such module "citation/CS1".
  30. Script error: No such module "citation/CS1".
  31. Script error: No such module "citation/CS1".
  32. Script error: No such module "citation/CS1".
  33. Script error: No such module "citation/CS1".
  34. Script error: No such module "citation/CS1".
  35. Script error: No such module "citation/CS1".
  36. Script error: No such module "citation/CS1".
  37. Script error: No such module "citation/CS1".
  38. a b Script error: No such module "citation/CS1".
  39. Script error: No such module "citation/CS1".
  40. Script error: No such module "citation/CS1".
  41. Script error: No such module "citation/CS1".
  42. Script error: No such module "citation/CS1".
  43. Script error: No such module "citation/CS1".
  44. Script error: No such module "citation/CS1".
  45. Script error: No such module "citation/CS1".
  46. Script error: No such module "citation/CS1".
  47. Script error: No such module "citation/CS1".
  48. Script error: No such module "citation/CS1".
  49. Script error: No such module "citation/CS1".
  50. Script error: No such module "citation/CS1".
  51. Script error: No such module "citation/CS1".
  52. Script error: No such module "citation/CS1".
  53. Script error: No such module "citation/CS1".
  54. Script error: No such module "citation/CS1".
  55. Script error: No such module "citation/CS1".
  56. Script error: No such module "citation/CS1".
  57. Script error: No such module "citation/CS1".
  58. Script error: No such module "citation/CS1".
  59. Script error: No such module "citation/CS1".
  60. Script error: No such module "citation/CS1".
  61. Script error: No such module "citation/CS1".
  62. Script error: No such module "citation/CS1".
  63. Script error: No such module "citation/CS1".
  64. Script error: No such module "citation/CS1".
  65. Script error: No such module "citation/CS1".
  66. Script error: No such module "Citation/CS1".Template:Cbignore
  67. Script error: No such module "citation/CS1".
  68. Script error: No such module "Citation/CS1".Template:Cbignore
  69. Script error: No such module "Citation/CS1".Template:Cbignore
  70. Script error: No such module "Citation/CS1".Template:Cbignore
  71. Script error: No such module "citation/CS1".
  72. Script error: No such module "citation/CS1".
  73. Script error: No such module "citation/CS1".
  74. Script error: No such module "citation/CS1".
  75. Script error: No such module "citation/CS1".
  76. Script error: No such module "citation/CS1".
  77. Script error: No such module "citation/CS1".
  78. Script error: No such module "citation/CS1".
  79. Script error: No such module "citation/CS1".
  80. Script error: No such module "citation/CS1".
  81. Script error: No such module "citation/CS1".
  82. Script error: No such module "citation/CS1".
  83. Script error: No such module "citation/CS1".
  84. Script error: No such module "citation/CS1".
  85. Script error: No such module "citation/CS1".
  86. Script error: No such module "citation/CS1".
  87. Script error: No such module "citation/CS1".
  88. Script error: No such module "citation/CS1".
  89. Script error: No such module "citation/CS1".
  90. Script error: No such module "citation/CS1".
  91. Script error: No such module "citation/CS1".
  92. Script error: No such module "citation/CS1".
  93. Script error: No such module "citation/CS1".
  94. Script error: No such module "citation/CS1".
  95. Script error: No such module "citation/CS1".
  96. Script error: No such module "citation/CS1".
  97. Script error: No such module "citation/CS1".
  98. Script error: No such module "citation/CS1".
  99. a b Script error: No such module "citation/CS1".
  100. Script error: No such module "citation/CS1".
  101. Script error: No such module "citation/CS1".
  102. Script error: No such module "citation/CS1".
  103. Script error: No such module "citation/CS1".
  104. Script error: No such module "citation/CS1".
  105. Script error: No such module "citation/CS1".
  106. Script error: No such module "citation/CS1".
  107. Script error: No such module "citation/CS1".
  108. Script error: No such module "citation/CS1".
  109. Script error: No such module "citation/CS1".
  110. Script error: No such module "citation/CS1".
  111. Script error: No such module "citation/CS1".
  112. Script error: No such module "citation/CS1".
  113. Script error: No such module "citation/CS1".
  114. Script error: No such module "citation/CS1".
  115. Script error: No such module "citation/CS1".
  116. Script error: No such module "citation/CS1".
  117. Script error: No such module "citation/CS1".
  118. Script error: No such module "citation/CS1".
  119. a b c Script error: No such module "citation/CS1".
  120. Script error: No such module "citation/CS1".
  121. Script error: No such module "citation/CS1".
  122. Script error: No such module "citation/CS1".
  123. Script error: No such module "citation/CS1".
  124. Script error: No such module "citation/CS1".
  125. Script error: No such module "citation/CS1".
  126. Script error: No such module "citation/CS1".
  127. Script error: No such module "citation/CS1".
  128. Script error: No such module "citation/CS1".
  129. E-mail to the kde-cygwin mailing list by Chris January, 4 February 2003
  130. Script error: No such module "citation/CS1".
  131. Script error: No such module "citation/CS1".
  132. Script error: No such module "citation/CS1".
  133. Script error: No such module "citation/CS1".
  134. Script error: No such module "citation/CS1".
  135. Script error: No such module "citation/CS1".
  136. Script error: No such module "citation/CS1".
  137. Script error: No such module "citation/CS1".
  138. Script error: No such module "citation/CS1".
  139. Script error: No such module "citation/CS1".
  140. Script error: No such module "citation/CS1".
  141. Script error: No such module "citation/CS1".
  142. Template:Cite mailing list
  143. Script error: No such module "citation/CS1".
  144. Script error: No such module "citation/CS1".
  145. a b Script error: No such module "citation/CS1".
  146. Script error: No such module "citation/CS1".
  147. Script error: No such module "citation/CS1".
  148. Script error: No such module "citation/CS1".
  149. Script error: No such module "citation/CS1".
  150. Script error: No such module "citation/CS1".
  151. Script error: No such module "citation/CS1".
  152. Script error: No such module "citation/CS1".
  153. Script error: No such module "citation/CS1".