blind_html [Fwd: announcing availability of beta package to access java from window-Eyes]

  • From: Nimer <nimerjaber1@xxxxxxxxx>
  • To: blind_html@xxxxxxxxxxxxx
  • Date: Wed, 11 Feb 2009 11:28:32 -0700

Yes! No Java Bridge!

Nimer J

-------- Original Message --------
Subject: announcing availability of beta package to access java from window-Eyes
Date:   Wed, 11 Feb 2009 12:15:17 -0600
From:   Macarty, Jay {PBSG} <Jay.Macarty@xxxxxxxx>
Reply-To:       programmingblind@xxxxxxxxxxxxx
To:     programmingblind@xxxxxxxxxxxxx <programmingblind@xxxxxxxxxxxxx>



Now available on the GW-Micro Script central website is WE4Java 0.9.11. This package provides access to java applications using the COM interface of Window-Eyes 7.0 or higher.

A couple of notes regarding this software:

· It is still considered beta. While much java application GUI access is available, there are still some areas of development actively being worked on. I welcome all input as to functionality or suggestions but do offer the heads-up that the answer may come back “that hasn’t been completed; still working on it.”

· You should be running java 1.5 or higher to use this software.

· WE4Java does NOT use the java access bridge. In fact, if an existing accessibility.properties file is found for a given java environment, it will be renamed. If you depend heavily on the JAB and don’t want to manually switch back and forth, you may want to hold off on using WE4Java. I’m researching allowing the 2 technologies to co-exist but it’s a little messy.

· While WE4Java doesn’t have an installer that searches out your java runtime directories over the whole machine, it does have an installer that checks for the default java runtime or JDK listed in the registry and asks if you want to install there. The installer also lets you browse to a directory where you want the software install (the jar and dll files). If you have a running java application that isn’t speaking but you don’t quite know where the java runtime is located, simply start the application and then run the wE4Java java installer from the WE4Java start menu/programs group. It will detect the process ID of the running application and prompt you to ask if you want to install wE4Java there. The installer can become confused if it finds more than 1 running java process; so, try to make sure you only have 1 java program executing at the time you use this feature.

· WE4Java allows reading read-only text area fields by copying the data to a popup dialog where you can arrow through the text and copy it to the clipboard if you like.

· WE4Java will track actual mouse movements such as with the mouse or a touch-pad. However, keyboard commands such as read mouse line or word are not quite there as yet. You can, however, use the mouse movement keys (e.g., ctrl+shift+ up, down, left, or right arrows on the standard WinEyes layout) to move the mouse and hear what it moves to.

· The package comes with 2 sample java applications taken from the development kit demos. These are the java notepad application and the java swingset 2 demo. The swingset2 demo shows all different types of swing controls on 16 different windows (e.g., one for types of buttons, one for lists, one for combo boxes, etc.). This demo has been used during much of the product development as a testing tool.

· Braille support is under development. It is there to a degree but isn’t fully functional as yet.

Hope you find the beta useful and I look forward to any feedback.

NOTE: at present, there is an issue with downloading the package using Jamal’s Package Installer script. You need to download it directly from the GW Script central website.

blind_html
To unsubscribe, please send a blank email to
blind_html-request@xxxxxxxxxxxxx
with unsubscribe in the subject line.
To access the archives, please visit:
http://www.freelists.org/archive/blind_html

Thanks

Other related posts:

  • » blind_html [Fwd: announcing availability of beta package to access java from window-Eyes] - Nimer