Qt Bridges Documentation

Goal and motivation

What if you could write Qt Quick UI backends in your favorite programming language without knowing much of Qt API?

The previous question was the one that shaped the project goal and motivated its development. We want to bring Qt to many more languages.

Many UI frameworks, depending on the languages, force you to follow a specific idiom or structure that might feel unfamiliar or strange to your code. This has been an aspect to improve in the many Qt Language bindings projects where you need to cross the line and embrace Qt and C++ idioms.

Why not work on more Qt API bindings?

We have seen how complete Qt API bindings can play a crucial role in other ecosystems by being accepted as a professional approach to develop both commercial and community-based applications. However, it is important to note that the work to fully expose every Qt module, with all their classes, enums, properties, and methods, is significant, and it requires a long time to reach the needed maturity.

Scope and supported use cases

The initial scope of the project is to provide a simple way to expose data via a backend in a specific target language to a Qt Quick UI application.

This can be also understood as a simple way to feed QAbstractItemModel-derived models in a more transparent way by annotating classes that will contain both the data and the functionality.

Getting started

Different programming languages have different ways to get started with new frameworks. Qt Bridges is no exception.

For the initial milestones of the project, you need to have a Qt Installation in your system, but for the initial 1.0 release this would not be necessary, because dependencies will be included in each package.

In order to build each bridge to a specific Qt version (6.10+), refer to the following language instructions: