Cross-platform software libraries and APIs
Qt Creator IDE and productivity tools
UI Design tool for UI composition
for Qt projects
Digital advertising for UI apps
Usage intelligence for embedded devices
GUI test automation
Code coverage analysis
Test results management and analysis
Software static code analysis
Software architecture verification
The latest version of Qt.
Make the most of Qt tools, with options for commercial licensing, subscriptions, or open-source.
Explore Qt features, the Framework essentials, modules, tools & add-ons.
The project offers PySide6 - the official Python bindings that enhance Python applications.
Qt empowers productivity across the entire product development lifecycle, from UI design and software development to quality assurance and deployment. Find the solution that best suits your needs.
Insight into the evolution and importance of user-centric trends and strategies.
Learn how to shorten development times, improve user experience, and deploy anywhere.
Tips on efficient development, software architecture, and boosting team happiness.
Get the latest resources, check out upcoming events, and see who’s innovating with Qt.
Whether you're a beginner or a seasoned Qt pro, we have all the help and support you need to succeed.
January 20, 2011 by Kent Hansen | Comments
We want Qt to have the best possible JavaScript technology. To make this happen, we need the ability to make drastic changes to the implementation -- even replacing it -- underneath our public APIs. If an API exposes implementation details, that will cause us to limp.
From our extensive work with existing JavaScript engines (JavaScriptCore from the WebKit project, and V8 from Google), we're starting to get a very clear picture regarding which parts of QtScript's C++ API are "universally valid", and which are "universally headache-inducing" to our implementation.
We need a path towards re-enacting the "Run, Forrest, run!" scene from Forrest Gump. To this end, say hello to QTBUG-15571, which serves as a hub for collecting information about, and ultimately resolving, implementation-biased QtScript API. In an ideal world, nobody (other than Qt's own libraries and tools) would be relying on those parts, and we could just click the big "Obsolete" button. However, we don't know the extent of their usage. If you or someone you know is using the API in question, it would be of great help to us if you leave a comment in the corresponding JIRA sub-task. Maybe there are some use cases we missed, too.
Due to source and binary compatibility constraints, we can't (and won't) drop the offending API in Qt 4.x. But it may limp.
Download the latest release here: www.qt.io/download.
Qt 6.8 release focuses on technology trends like spatial computing & XR, complex data visualization in 2D & 3D, and ARM-based development for desktop.
Check out all our open positions here and follow us on Instagram to see what it's like to be #QtPeople.
Sep 20, 2024
Qt Gradle Plugin 1.0 (QtGP) build tool has been released. You can include..
Sep 16, 2024
We are happy to announce the release of Qt Tools for Android Studio 3.0...
Aug 30, 2024
Qt/.NET is a proposed toolkit for interoperability between C++ and .NET,..
Qt Group includes The Qt Company Oy and its global subsidiaries and affiliates.