Qt Jambi: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
No edit summary
(I updated this fully outdated description of QtJambi to its current situation.)
 
(7 intermediate revisions by 3 users not shown)
Line 1: Line 1:
[[Category:LanguageBindings::QtJambi]]
__NOTOC__


= Qt Jambi =
''QtJambi'' is a community-maintained open-source project that provides Java language bindings to the Qt APIs. The bindings are generated by inspection of the C++ header files of the Qt implementation then emitting code to provide the necessary JNI (Java Native Interface) and ''.java'' files to provide linkage to Java. An application programmer using Qt Jambi would simply add the coresponding Java libraries (''.jar'' files) to their Java project to be able to develop and deploy their application.


This is a community maintained project ('qtjambi-community') that provides Java language bindings to the Qt APIs. The bindings are generated by inspection of the C++ header files of the Qt implementation then emitting code to provide the necessary JNI (Java Native Interface) and '''.java files to provide linkage to Java. An application programmer using Qt Jambi would simply add the'''.jar files to their Java project to be able to develop and deploy their application.
Example:<syntaxhighlight lang="java">
import io.qt.widgets.*;
public class Test {
public static void main(String[] args) {
QApplication.initialize(args);
QMessageBox.information(null, "QtJambi", "Hello World!");
QApplication.shutdown();
}
}
</syntaxhighlight>The bindings implement typical C++-Qt features for Java like:


The bindings implement such things as signal/slot mechanics for Java and cross-thread marshaling of an event driven programming model. Indeed the API presented to the Java programmer is very similar to the C++ APIs so your knowledge of C++ can largely be transferred to Java. These alternative programming models maybe considered a new and refreshing choice for application developers looking for an alternative to the strict static type programming patterns employed by other Java UI toolkits. Qt Jambi makes use of Java reflection and can integrate with the QMetaObject system (that provides similar reflection mechanism to C+''). However it does not preclude the use of any Java patterns from your application design Qt Jambi provides additional ways to program java.
* signal/slot mechanism
* meta object properties
* thread-affinity, multithreading, cross-thread marshaling
* resource management
* internationalization
* interfaces
* containers
* function pointers
* QML / Java interoperability
* and more


There is much overlap with some Qt modules with already existing Java APIs and 3rd party libraries. Qt Jambi does not inhibit or restrict the implementation of a feature you choose to use. Some of the strengths of Qt to Java are in the cross-platform UI toolkit, the programming model, UI scripting support, embedded web browser support.
Indeed the API presented to the Java programmer is very similar to the C++ APIs so your knowledge of C++ can largely be transferred to Java. These alternative programming models maybe considered a new and refreshing choice for application developers looking for an alternative to the strict static type programming patterns employed by other Java UI toolkits. Qt Jambi makes use of Java reflection and can integrate with the QMetaObject system (that provides similar reflection mechanism to C+)''.''


The qtjambi-community source project integrates with all Qt versions between 4.5 and 4.8'', this includes, 4.6 and 4.7. Work on Qt5 is planned but not until the release of 5.1 where Qt on the desktop will get attention. One aspect of the project is that due to the generation technique bug fixes applied to the project can still be used with all supported Qt versions, there is no need to back-port such fixes. Simply rebuild the project against the version of Qt you wish to use.


Another feature of the project is that it is possible to reuse your custom C++ QWidget's and other QPlugins with Qt Jambi. If your objects expose QMetaObject they may simply work as the java bindings are able to invoke and integrate with QMetaObject. Alternatively you can use the generator (provided in the Qt Jambi project) to expose Java API bindings for your custom plugins, an example of this is provided in the project sources. This allows you to combine the benefit of C++ performance in areas where it is needed with the rapid application development enjoyed by Java developers.
There is much overlap with some Qt modules with already existing Java APIs and 3rd party libraries. Qt Jambi does not inhibit or restrict the implementation of a feature you choose to use. However, the combination of Qt and other UI toolkits in the same application is technically limited. Some of the strengths of Qt to Java are in the cross-platform UI toolkit, the programming model, UI scripting support, embedded web browser support.


The Community website for Qt Jambi can be found at "Qt Jambi Community's website.":http://qt-jambi.org


The Community bug tracker: "Qt Jambi Community bug tracker":http://redmine.smar.fi/projects/qtjambi/issues
Another feature of the project is that it is possible to reuse your custom C++ QWidget's and other QPlugins with Qt Jambi. If your objects expose QMetaObject they may simply work as the java bindings are able to invoke and integrate with QMetaObject. Alternatively you can use the generator (provided in the Qt Jambi project) to expose Java API bindings for your custom C++ library. This allows you to combine the benefit of C++ performance in areas where it is needed with the rapid application development enjoyed by Java developers.


The Community patch submission: "Qt Jambi Community gerrit":http://gerrit.smar.fi/#/q/status:open+project:qtjambi-community,n,z
==Qt Jambi past==


== Qt Jambi past ==
Before March 2009 the project ('qt-jambi') was maintained and released by Trolltech, their latest release was Qt Jambi 4.5.2_01 based on a port of Qt 4.5.2. This is last version by the Qt team (based at Trolltech). When Nokia purchased Trolltech the Qt Jambi project was not put into the future road map so the work was spun off into the open source project. The source code project that is called 'qt-jambi' is from this pre March 2009 era and does not support any version of Qt 4.7 or later. The successor open source project 'https://github.com/qtjambi/qtjambi<nowiki/>' continued support for all Qt versions between 4.5 and 4.8.


Before March 2009 the project ('qt-jambi') was maintained and released by Trolltech, their latest release was Qt Jambi 4.5.2_01 based on a port of Qt 4.5.2. This is last version by the Qt team (based at Trolltech). When Nokia purchased Trolltech the Qt Jambi project was not put into the future road map so the work was spun off into the open source project. The source code project that is called 'qt-jambi' is from this pre March 2009 era and does not support any version of Qt 4.7 or later.
==Binaries==


== Binaries ==
[https://github.com/OmixVisualization/qtjambi/releases QtJambi Releases]


"Qt Jambi Community Releases":http://qt-jambi.org/downloads
==Repository==


== Old Binaries (not maintained since March 2009) ==
https://github.com/OmixVisualization/qtjambi ''this source tree is actively being developed''


"Qt Jambi 4.5.2_01Binary for Windows 32-bit":http://get.qt.nokia.com/qtjambi/source/qtjambi-win32-lgpl-4.5.2_01.zip
==See also==
"Qt Jambi 4.5.2_01Binary for Windows 64-bit":http://get.qt.nokia.com/qtjambi/source/qtjambi-win64-lgpl-4.5.2_01.zip
"Qt Jambi 4.5.2_01Binary for Mac":http://get.qt.nokia.com/qtjambi/source/qtjambi-mac-lgpl-4.5.2_01.tar.gz
"Qt Jambi 4.5.2_01Binary for Linux/X11 32-bit":http://get.qt.nokia.com/qtjambi/source/qtjambi-linux32-lgpl-4.5.2_01.tar.gz
"Qt Jambi 4.5.2_01Binary for Linux/X11 64-bit":http://get.qt.nokia.com/qtjambi/source/qtjambi-linux64-lgpl-4.5.2_01.tar.gz
 
== Old Eclipse Integation (not maintained since March 2009) ==
 
"Qt Jambi 4.5.2_01 for Linux/X11 32-bit":http://get.qt.nokia.com/qtjambi/source/qtjambi-eclipse-integration-linux32-4.5.2_01.tar.gz
"Qt Jambi 4.5.2_01 for Windows":http://get.qt.nokia.com/qtjambi/source/qtjambi-eclipse-integration-win32-4.5.2_01.zip
 
== Old Source Package (not maintained since March 2009) ==
 
"Qt Jambi 4.5.2_01 Source Package (tar.gz)":http://get.qt.nokia.com/qtjambi/source/qtjambi-src-lgpl-4.5.2_01.tar.gz
"Qt Jambi 4.5.2_01 Source Package (zip)":http://get.qt.nokia.com/qtjambi/source/qtjambi-src-lgpl-4.5.2_01.zip
 
== Repository ==
 
"http://qt.gitorious.org/qt-jambi/qtjambi-community":http://qt.gitorious.org/qt-jambi/qtjambi-community ''this source tree is actively being developed''
 
"http://qt.gitorious.org/qt-jambi/qt-jambi":http://qt.gitorious.org/qt-jambi/qt-jambi ''this source tree has not been maintained since March 2009''
 
== Ubuntu (PPA from Launchpad) ==
 
It is best to read download and install instructions in PPA description at:
 
"Qt Jambi Snaphosts for Ubuntu":http://launchpad.net/~qtjambi-community/+archive/libqtjambi-snapshots
 
This tries to cover all recent Ubuntu releases and LTS releases that are compatible with Qt Jambi project.
 
== OBS (OpenSuSE build system, including Fedora/Red Hat/CentOS and SLS/OpenSuSE) ==
 
"Qt Jambi Snapshots for Linux":https://build.opensuse.org/package/show?package=qtjambi-snapshots&amp;amp;project=home:dlmiles:qtjambi-community
 
See OBS wiki and documentation for how to add a custom repository to your distribution. Then you can download, update and install via your Linux package manager.
 
== Mailing List ==
 
"Qt-jambi-interest Archives and Subscription":http://lists.qt.nokia.com/mailman/listinfo/qt-jambi-interest
 
== See also ==


This page describes the Java bindings. There is also QtScript which is the JavaScript bindings. Similar sounding technologies, but very different :)
This page describes the Java bindings. There is also QtScript which is the JavaScript bindings. Similar sounding technologies, but very different :)

Latest revision as of 08:13, 10 May 2021


QtJambi is a community-maintained open-source project that provides Java language bindings to the Qt APIs. The bindings are generated by inspection of the C++ header files of the Qt implementation then emitting code to provide the necessary JNI (Java Native Interface) and .java files to provide linkage to Java. An application programmer using Qt Jambi would simply add the coresponding Java libraries (.jar files) to their Java project to be able to develop and deploy their application.

Example:

import io.qt.widgets.*;
public class Test {
	public static void main(String[] args) {
		QApplication.initialize(args);
		QMessageBox.information(null, "QtJambi", "Hello World!");
		QApplication.shutdown();
	}
}

The bindings implement typical C++-Qt features for Java like:

  • signal/slot mechanism
  • meta object properties
  • thread-affinity, multithreading, cross-thread marshaling
  • resource management
  • internationalization
  • interfaces
  • containers
  • function pointers
  • QML / Java interoperability
  • and more

Indeed the API presented to the Java programmer is very similar to the C++ APIs so your knowledge of C++ can largely be transferred to Java. These alternative programming models maybe considered a new and refreshing choice for application developers looking for an alternative to the strict static type programming patterns employed by other Java UI toolkits. Qt Jambi makes use of Java reflection and can integrate with the QMetaObject system (that provides similar reflection mechanism to C+).


There is much overlap with some Qt modules with already existing Java APIs and 3rd party libraries. Qt Jambi does not inhibit or restrict the implementation of a feature you choose to use. However, the combination of Qt and other UI toolkits in the same application is technically limited. Some of the strengths of Qt to Java are in the cross-platform UI toolkit, the programming model, UI scripting support, embedded web browser support.


Another feature of the project is that it is possible to reuse your custom C++ QWidget's and other QPlugins with Qt Jambi. If your objects expose QMetaObject they may simply work as the java bindings are able to invoke and integrate with QMetaObject. Alternatively you can use the generator (provided in the Qt Jambi project) to expose Java API bindings for your custom C++ library. This allows you to combine the benefit of C++ performance in areas where it is needed with the rapid application development enjoyed by Java developers.

Qt Jambi past

Before March 2009 the project ('qt-jambi') was maintained and released by Trolltech, their latest release was Qt Jambi 4.5.2_01 based on a port of Qt 4.5.2. This is last version by the Qt team (based at Trolltech). When Nokia purchased Trolltech the Qt Jambi project was not put into the future road map so the work was spun off into the open source project. The source code project that is called 'qt-jambi' is from this pre March 2009 era and does not support any version of Qt 4.7 or later. The successor open source project 'https://github.com/qtjambi/qtjambi' continued support for all Qt versions between 4.5 and 4.8.

Binaries

QtJambi Releases

Repository

https://github.com/OmixVisualization/qtjambi this source tree is actively being developed

See also

This page describes the Java bindings. There is also QtScript which is the JavaScript bindings. Similar sounding technologies, but very different :)