Languages/Java: Difference between revisions

From KDE TechBase
No edit summary
No edit summary
 
(5 intermediate revisions by 5 users not shown)
Line 1: Line 1:
'''Note: This page is very old and does not apply to at all to the current state of KDE software.'''
Java support for KDE is now fairly significant. You can add applet support to your KDE applications, and with the Qt/KDE Java bindings you can develop KDE apps in Java. Issues relating to Java support for KDE should be discussed on the kde-java mailing list (though applet issues are usually discussed on kfm-devel).
* [http://developer.kde.org/language-bindings/java/qtjava.html QtJava and KDEJava (Koala)]<br /> The QtJava and KDEJava (Koala) bindings developed by Richard Dale allow you to create Qt and KDE applications using Java. The code uses JNI to allow Java code to access KDEs native widgets. These bindings can be found in the [http://websvn.kde.org/trunk/KDE/kdebindings/ kdebindings module] of the KDE Subversion repository ([http://developer.kde.org/source/anonsvn.html Instructions]).
* [http://developer.kde.org/language-bindings/java/kjas/index.html KDE Java Applet Server (KJAS)]<br />KJAS allows KDE applications to embedd Java applets. It uses a pure Java server to run the applets, which it communicates with using standard UNIX pipes. KDE programmers can use a special KJavaAppletWidget to display the applets in their application. KJAS is already in a usable state.
* [http://developer.kde.org/language-bindings/java/qtawt/index.html QtAWT]<br />The QtAWT is a port of the peer classes underlying the Java AWT to the Qt toolkit, in future it will also use the KDE widgets. QtAWT is currently very incomplete, but you should feel free to give it a try, or even better to help finish it.
* [https://mail.kde.org/mailman/listinfo/kde-java Mailing List] ([http://mail.kde.org/pipermail/kde-java/ Archives]) <br />There is a dedicated mailing list for Java-specific issues in KDE. It is a fairly low-traffic list aimed at developers with an interest in writing Java applications for KDE and/or writing and maintaining the Java bindings.
* [http://doc.trolltech.com/qtjambi-1.0.0beta/com/trolltech/qt/qtjambi-index.html Qt Jambi Reference Documentation]
* [http://doc.trolltech.com/qtjambi-1.0.0beta/com/trolltech/qt/qtjambi-index.html Qt Jambi Reference Documentation]
* [http://www.trolltech.com/pdf/qtjambi-whitepaper-tp3.pdf Qt Jambi Whitepaper]
* [http://www.trolltech.com/pdf/qtjambi-whitepaper-tp3.pdf Qt Jambi Whitepaper]

Latest revision as of 20:32, 28 March 2016

Note: This page is very old and does not apply to at all to the current state of KDE software.

Java support for KDE is now fairly significant. You can add applet support to your KDE applications, and with the Qt/KDE Java bindings you can develop KDE apps in Java. Issues relating to Java support for KDE should be discussed on the kde-java mailing list (though applet issues are usually discussed on kfm-devel).

  • QtJava and KDEJava (Koala)
    The QtJava and KDEJava (Koala) bindings developed by Richard Dale allow you to create Qt and KDE applications using Java. The code uses JNI to allow Java code to access KDEs native widgets. These bindings can be found in the kdebindings module of the KDE Subversion repository (Instructions).
  • KDE Java Applet Server (KJAS)
    KJAS allows KDE applications to embedd Java applets. It uses a pure Java server to run the applets, which it communicates with using standard UNIX pipes. KDE programmers can use a special KJavaAppletWidget to display the applets in their application. KJAS is already in a usable state.
  • QtAWT
    The QtAWT is a port of the peer classes underlying the Java AWT to the Qt toolkit, in future it will also use the KDE widgets. QtAWT is currently very incomplete, but you should feel free to give it a try, or even better to help finish it.
  • Mailing List (Archives)
    There is a dedicated mailing list for Java-specific issues in KDE. It is a fairly low-traffic list aimed at developers with an interest in writing Java applications for KDE and/or writing and maintaining the Java bindings.