Yes. Because WBI is written in Java, WBI plugins can use native code through the Java Native Interface (JNI). The example History plugin does this. Native code should reside in special subdirectories. We provide a method Proxy.getNativePath() that allows you to write platform independent Java code for loading native libraries. The idea is to separate native code into platform dependent subdirectories.

No. WBI Development Kit for Java is being distributed only in binary (class) form. We are considering an open-source distribution of WBI Development Kit for Java. If you think this is a good idea and would like us to do so, please send email to wbi-license@almaden.ibm.com. You may use WBI Development Kit for Java for your research and for building innovative plug-ins that demonstrate your ideas. You may set up a WBI Development Kit for Java server that others can access to use your plug-in.

Once you have downloaded WBI from alphaWorks, you need to unzip the files and configure your system. For more information on how to do that, see the Quick Start documentation.

You can use Java Web Start to deploy Java Technology-based applications that depend on native code such as DLLs and SOs. Use the <nativelib ...> element to specify required native libraries. See the Developer's Guide for details. Java Web Start uses a user-level classloader to load all the application resources specified in the JNLP file. This classloader implements the security model and the downloading model defined by the JNLP specification.

Not yet... but I am working on making the softare public domain, and building a Mac OS X version which may be out in March 2005. The Simulator is not 100% bug free (especially when viewing Saturn very zoomed in or in certain geometries). Try again from a slightly different viewpoint or field of view. There is a bug list that gets worked on every couple of months.

The plugin implementation in Flock is essentially the same as in Firefox, which means third party plugins designated for Mozilla Firefox also work for Flock.

No. WBI is only being distributed in binary (class) form. We are considering an open-source distribution of WBI. If you think this is a good idea and would like us to do so, please send email to wbi-license@almaden.ibm.com. You may use WBI for your research, building innovative plugins that demonstrate your ideas. You may setup a WBI server that others can access to use your plugin. You may do this for research and non-commercial purposes only.

While WBI Development Kit for Java is running, you can interact with it via a command-line interface called the WBI Development Kit for Java console or through WBI Development Kit for Java's new Graphical User Interface (GUI). Through the console or the GUI, you can register or deregister plug-ins, enable or disable plug-ins, find out which port WBI Development Kit for Java is listening to, and list registered plug-ins and MEGs.

Technically, no. We cannot guarantee bug fixes or enhancements at this time. We do intend to continue improving and enhancing WBI Development Kit for Java, so we are very interested in your feedback. If you have questions, problems, or suggestions, please send email to wbi-developer@almaden.ibm.com. We cannot guarantee a satisfactory response, but we want WBI Development Kit for Java to useful to you.

The neTVision Video Player uses the Java Native Interfaces to execute native code on the clients machine. The neTVision Video Player requests the user's permission to run native code (outside the Java environment), and this is why the user observes a security warning prompt. We do this to optimise the playback experience for the user.

We ask that you turn off all other spam plugins as they may reduce the effectiveness of Akismet. Besides, you shouldn't need them anymore! :) But if you are investigating alternatives, we recommend checking out Bad Behavior and Spam Karma, both which integrate with Akismet nicely. Yes, our system does not discriminate against non-English comments. We have happy users from Japan to France.

You can use bridging software to use other vendors' COM classes in your programs written for the Java Platform and to interface with third-party software. The bridging software you choose will need to suit the JVM software version you are using, as well as the application that you want to interface with. Following is a listing of bridging software:

No. Plugins developed with the original version of the WBI Development Kit, version 4.1, cannot be used as is with the new DK download, version 4.5 (or the previous versions 4.4 and 4.3). However, it takes only a few minutes to port your plugins from 4.1 to 4.3 if you follow our notes on porting. Little porting should be needed to move from 4.3 to 4.4 or 4.4 to 4.5 --- only if you used the old Database API, which has been removed in favor of the new Persistence classes.

We wanted to provide the simplest possible start for developers; shipping a complete Java implementation was the easiest way to do that. The custom Java client also has some convenience features such as default values for seldom-used parameters.

Select Programs at the Start button to display the MS Office programs that are available. You may also select Programs and Plugins at the Library Resources tab on iGEMS.

Download and install a host software, then download and install the plugins from our page. They will appear in the host "effects" menu. If you are using a DirectX host with our MIDI controllable plugins and they do not show up in you host list, you might need to use our freeware DXi Manager.

Yes you can - although SwingWT closely resembles the Swing/AWT APIs, you can access the SWT widgets with a call to getSWTPeer() for any component and getComposite() for any container. This works two ways, and you can wrap up an existing SWT widget with a SwingWT one. To add a SwingWT container (eg: JPanel) to an SWT container, simply create the SWT container, then create a new swingwt.awt.Container object and assign the SWT container to it. You can then treat it like any other Swing container.

clearly indicated in class, you may NOT use Java's hashtable class. The goal of this lab is for you to write your own hashtable class.

The client and server software need Java 1.4.2 (or higher). The servlets require the Java Servlet library which is available from Java.com in the Java Enterprise Edition (J2EE), or via downloading a servlet engine such as Apache Tomcat.

No. Policies develop over time and new restrictions are introduced gradually. For example, it was possible in the past to register names corresponding to airport codes by other aviation entities. Today, under the new policy, this is no longer possible. SITA will not cancel domain names because the rules have changed.

WBI Development Kit for Java was developed in the USER Group in the Computer Science Department at IBM Almaden Research Center.

For technical or programming questions, write to wbi-developer@almaden.ibm.com. For business or licensing questions, write to wbi-license@almaden.ibm.com.

This behavior can be caused by many things. Make sure that you are in the WBI Development Kit for Java home directory and that you used the command "Run". If you tried to start the program by using "Java Run", then you should make sure that your classpath is set correctly. (The classpath must include the WBI Development Kit for Java JAR files.) Make sure that you have Sun's Java 2 SDK (or other Java run-time system) installed on your machine.

To register or deregister a WBI Development Kit for Java plug-in, use the WBI Development Kit for Java console. To register a plug-in, use the command "register" followed by the path to the plug-in's .reg file. You can also register the default plug-in by using the command "register default". To deregister a plug-in, use the command "deregister" followed by the complete class name of the plug-in (including the package name). To deregister all plug-ins, use the command "deregister all".

Several configuration files in the directory etc/config/wbi/ control WBI Development Kit for Java's operation as well as details such as how WBI Development Kit for Java should work with firewall machines, such as Socks servers and other proxies.

WBI Development Kit for Java is available on alphaWorks so that anyone can download it, use it for personal use, and develop their own plug-ins. Use the WBI Development Kit for Java software at your risk. It can be used to develop your own plug-ins, which can be distributed under whatever terms you specify. However, the license does not allow you to distribute WBI Development Kit for Java with your plug-in. You can do one of two things: Send email to wbi-license@almaden.ibm.

Figments of imagination are preceded by **, unless the reader isn't supposed to know it's imagination and it isn't painfully obvious.

The source code for PGP 2.3a and earlier is distributed under GPL - the General Public License - so it can be used freely in your own programs. The source code for PGP 2.6 and later may be used as a whole in unmodified form in products you write for your own non-commercial use under the terms of PGP's non-commercial source code license for PGP 5.0i.

You do not sell or republish the code or it's associated article without the author's written agreement Some authors may also have specific restrictions on using code in commercial apps such as providing credit in documentation or sending them an email first. When you sign up for the newsletter you automatically get a user account on CodeProject. This account allows you to customize your settings, such as: Your discussion board name and signature.