Jump to content

Java Desktop Integration Components: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
Cydebot (talk | contribs)
m clean up per WP:CHECKWIKI, typo(s) fixed: As a result → As a result, using AWB
Line 1: Line 1:
{{Morefootnotes|date=June 2010}}
{{More footnotes|date=June 2010}}


The '''Java Desktop Integration Components''' ('''JDIC''') project provides components which give [[Java (programming language)|Java]] applications the same access to [[operating system]] services as native applications. For example, a Java application running on one user's desktop can open a web page using that user's default [[web browser]] (e.g. [[Firefox]]), but the same Java application running on a different user's desktop would open the page in [[Opera (web browser)|Opera]] (the second user's default browser).
The '''Java Desktop Integration Components''' ('''JDIC''') project provides components which give [[Java (programming language)|Java]] applications the same access to [[operating system]] services as native applications. For example, a Java application running on one user's desktop can open a web page using that user's default [[web browser]] (e.g. [[Firefox]]), but the same Java application running on a different user's desktop would open the page in [[Opera (web browser)|Opera]] (the second user's default browser).
Initially the project supports features such as embedding the native [[web browser|HTML browser]], programmatically opening the native [[Email client|mail client]], using registered file-type viewers, and packaging JNLP applications as RPM, SVR4, and [[Windows Installer|MSI]] [[installer|installer package]]s. As a bonus, an [[Software development kit|SDK]] for developing platform-independent [[screensaver]]s is included.
Initially the project supports features such as embedding the native [[web browser|HTML browser]], programmatically opening the native [[Email client|mail client]], using registered file-type viewers, and packaging JNLP applications as RPM, SVR4, and [[Windows Installer|MSI]] [[installer|installer package]]s. As a bonus, an [[Software development kit|SDK]] for developing platform-independent [[screensaver]]s is included.
<ref>http://javadesktop.org/articles/jdic/index.html JavaDesktop: The JDIC Project</ref>
<ref>http://javadesktop.org/articles/jdic/index.html JavaDesktop: The JDIC Project</ref>
Most of the features provided by JDIC were incorporated into the [[Java Development Kit|JDK]] starting with version 1.6. As a result the development of the project has come to an end.
Most of the features provided by JDIC were incorporated into the [[Java Development Kit|JDK]] starting with version 1.6. As a result, the development of the project has come to an end.


== Components ==
== Components ==
Line 11: Line 11:
*jdic.dll and tray.dll: On [[Microsoft Windows|Windows]] installations, these files need to be into the directory where this operating system is installed (normally, C:\Windows). They contain the "bridge" methods between the jdic.jar Java methods and the native OS methods.
*jdic.dll and tray.dll: On [[Microsoft Windows|Windows]] installations, these files need to be into the directory where this operating system is installed (normally, C:\Windows). They contain the "bridge" methods between the jdic.jar Java methods and the native OS methods.
*libjdic.so and libtray.so: On [[Solaris (operating system)|Solaris]] and [[GNU/Linux]] operating systems, these two files must go into the LD_LIBRARY_PATH folder.
*libjdic.so and libtray.so: On [[Solaris (operating system)|Solaris]] and [[GNU/Linux]] operating systems, these two files must go into the LD_LIBRARY_PATH folder.

== References ==
{{reflist}}


== See also ==
== See also ==
{{Portal|Free Software}}
{{Portal|Free Software|Java}}
{{Portal|Java}}
* [[Java Desktop]]
* [[Java Desktop]]

== References ==
{{reflist}}


== External links ==
== External links ==

Revision as of 03:20, 13 September 2015

The Java Desktop Integration Components (JDIC) project provides components which give Java applications the same access to operating system services as native applications. For example, a Java application running on one user's desktop can open a web page using that user's default web browser (e.g. Firefox), but the same Java application running on a different user's desktop would open the page in Opera (the second user's default browser). Initially the project supports features such as embedding the native HTML browser, programmatically opening the native mail client, using registered file-type viewers, and packaging JNLP applications as RPM, SVR4, and MSI installer packages. As a bonus, an SDK for developing platform-independent screensavers is included. [1] Most of the features provided by JDIC were incorporated into the JDK starting with version 1.6. As a result, the development of the project has come to an end.

Components

The cross-platform JDIC package, which files should allow the user to work, includes:[2]

  • jdic.jar: JAR file which contains all the Java classes needed for development. It must be in the classpath of the user for compilation.
  • jdic.dll and tray.dll: On Windows installations, these files need to be into the directory where this operating system is installed (normally, C:\Windows). They contain the "bridge" methods between the jdic.jar Java methods and the native OS methods.
  • libjdic.so and libtray.so: On Solaris and GNU/Linux operating systems, these two files must go into the LD_LIBRARY_PATH folder.

See also

References

  1. ^ http://javadesktop.org/articles/jdic/index.html JavaDesktop: The JDIC Project
  2. ^ http://www.ibm.com/developerworks/java/library/j-jdic/ Integrate native OS features in your desktop applications with JDIC