JavaSoft - 
Sun MicroSystems
JAVA ACCESSIBILITY
Java Accessibility Explorer Tool
Version 0.5
08 October 1997

[Home] [What is it?] [Overview of API Features] [API Reference]
[FAQ] [Tutorial] [Tools] [Changes] [JFC Home Page]

Explorer keeps track of the mouse movement in a particular Java Virtual Machine. When detects the mouse has stopped moving for a short period of time, it calls EventQueueMonitor's method, getAccessibleAt, to determine the Accessible object under the mouse. Once it has done so, it displays the Accessible information of that object.

Snap shot of Explorer in action.

Preparing Run Explorer:

The Explorer class is in the examples/Explorer directory included with this release of Java Accessibility (click here to view the source). Before you can run it, you need to set up your environment appropriately by following these instructions:

  • Modify your CLASSPATH environment variable so that the jaccess.jar (e.g., jaccess-0.5/jaccess.jar or jaccess-0.5\jaccess.jar) file that comes with this prerelease kit is included in the path.
  • Modify your CLASSPATH environment variable so that the Explorer directory (e.g., jaccess-0.5/examples/Explorer or jaccess-0.5\examples\Explorer) is included in the path.
  • Modify your $JDKHOME/lib/awt.properties file (e.g., jdk1.1.2/lib/awt.properties or C:\jdk1.1.2\lib\awt.properties) to include the following lines (a sample awt.properties can be found here):
  • AWT.EventQueueClass=com.sun.java.accessibility.EventQueueMonitor
    AWT.AutoLoadClasses=Explorer

    After you follow these instructions, you should be ready to run Explorer. If you did not set up your CLASSPATH correctly you might get one of the following errors when running a Java application:

    Failed loading com.sun.java.accessibility.EventQueueMonitor: java.lang.ClassNotFoundException: com.sun.java.accessibility.EventQueueMonitor
    Error trying to newInstance Explorer java.lang.ClassNotFoundException: Explorer

    The first error means that the jaccess.jar file is not in your CLASSPATH, and the second that the Explorer directory is not in your CLASSPATH.

    Running Explorer:

    By following the instructions above, Explorer will automatically be started any time you start a Java application in a virtual machine. For example, if you run the "SwingSet" demonstration application that comes with the prerelease of the JFC (swing-0.5), Explorer will automatically start.

    Using Explorer:

    Explorer doesn't require you to do anything except move the mouse. Once you stop moving the mouse, Explorer will use the EventQueueMonitor class to determine the Accessible object under the mouse pointer. Once it does so, it will call each Accessible method on that object and display the results.

    NOTE: This is a preliminary release of Java Accessibility. We reserve the right to modify the specification in future versions.


    Java Logo Copyright© 1995-97 Sun Microsystems, Inc. All Rights Reserved.
    To submit comments or suggestions about Java Accessibility, please send mail to access@sun.com.

    Sun 
MicroSystems