RE: Java accessibility

From: "Macarty, Jay {PBSG}" <Jay.Macarty@xxxxxxxx>
To: "programmingblind@xxxxxxxxxxxxx" <programmingblind@xxxxxxxxxxxxx>
Date: Mon, 4 May 2009 01:35:22 -0500
Lloyd,
I haven't heard of this option but will look to see if I can find out how to 
disable it if desired. 


-----Original Message-----
From: programmingblind-bounce@xxxxxxxxxxxxx 
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Lloyd Rasmussen
Sent: Thursday, April 30, 2009 6:28 PM
To: programmingblind@xxxxxxxxxxxxx
Subject: RE: Java accessibility

I will see you at the NFBCS meeting.  

I recently installed your script for Java, and can indeed read the Java Control 
Panel in Window-Eyes.  But this leads to a question.

I was looking at running processes on my PC at work (and found this at home 
also), and discovered a recently added program, jqs.exe, Java Quick Start.
Some info on an internet forum indicated that this is a program which 
pre-fetches many Java components in versions of Windows before Vista, so that 
when it is needed, Java will load faster.  Is there any way to disable this 
program, to prevent some disk thrashing, with or without use of the Java 
Control Panel?  I think this pre-fetch mechanism was incorporated into the Java 
runtimes some time last year.

Lloyd Rasmussen, W3IUU, Kensington, Maryland
Home:  http://lras.home.sprynet.com
Work:  http://www.loc.gov/nls
 

> -----Original Message-----
> From: programmingblind-bounce@xxxxxxxxxxxxx [mailto:programmingblind- 
> bounce@xxxxxxxxxxxxx] On Behalf Of Macarty, Jay {PBSG}
> Sent: Wednesday, April 29, 2009 10:04 AM
> To: programmingblind@xxxxxxxxxxxxx
> Subject: RE: Java accessibility
> 
> Susie,
> 
> As Sina indicates, I have written the current Window-Eyes access for Java.
> It is still a work-in-progress but is coming along. In fact, I will be 
> speaking at the NFB convention this July to the Computer Science group 
> regarding my work on Window-Eyes Java accessibility.
> 
> One thing to note is that a primary difference between the Jaws Java 
> access and the Window-Eyes java access is that the Jaws java access 
> has a dependency on the Java Access Bridge while the Window-Eyes 
> solution does not. The java swing API contains an extremely powerful 
> accessibility framework. The Java Access Bridge makes use of this 
> framework but it isn't the only mechanism for accessing it. When I 
> first released some of the early beta copies of the window-Eyes java 
> access tool, I had a long conversation with Peter Korn from Sun 
> regarding the architecture of the WE4Java support and how it works. He was in 
> agreement with the approach.
> 

__________
View the list's information and change your settings at 
//www.freelists.org/list/programmingblind

__________
View the list's information and change your settings at
//www.freelists.org/list/programmingblind
RE: Java accessibility

Other related posts:
