headers
Padraig O'Briain | 1 Nov 2004 11:01
Picon

Re: Java-access-bridge INSTALL Discrepency

The text in the INSTALL file is wrong. I have updated it in CVS . I have
attached the new version to this mail.

Padraig

Janina Sajka wrote:

>I built the current java-access-bridge (from ftp.gnome.org) and ran into
>a discrepency. I'm not sure what to do? Where does this file actually
>belong?
>
>The INSTALL guidance and the output of "make install" appear to be at
>odds. INSTALL says:
>
>(4) run make install; you may need to change permissions on the
>directory $JAVA_HOME/jre/lib, or else manually install or edit the
>file "accessibility.properties" in that directory.  Note that
>this installation overwrites that file, so if it exists already you
>may wish to hand edit it instead.
>
>Setting aside any issue about "hand-editing" for the moment, this is at
>odds with the current 'make install' which attempts (and, under Fedora
>fails) to install this file in /usr/share jar.
>
>Which is correct? Where does this belong?
>
>
>  
>
(Continue reading)

Permalink | Reply | 7 comments |
headers
Janina Sajka | 1 Nov 2004 14:37

Re: Java-access-bridge INSTALL Discrepency

Thanks, Padraig. Unfortunately, I see two typos in the new guidance
below--at least, I think they're typos:

Padraig O'Briain writes:
> The text in the INSTALL file is wrong. I have updated it in CVS . I have
> attached the new version to this mail.
> 
... snip snip ...
> 
> You may optionally include a java_home environment variable:
> 
> 	./autogen.sh --prefix=/opt/gnome-2.0 --with-java-home=/usr/java/j2sdk1.4.0
> 
> (2a) If you obtained the java-access-bridge via a tarfile,
> run "./configure" in this directory with options as above.
> 
> (3) run make to build gnome-java-access.tar.  You will need 
> a Java Virtual Machine version 1.4.0 beta4 or higher.  
> 
> (4) run make install. 
> 
> (5) before running a Java program with the Java Access Bridge, you
> will need to make sure that your GNOME 2 installation enables
> CORBA traffic over IP from the ORBit2 ORB.  Do this by including
> the following line in a file, ".orbitrc" in your home directory:
> 
> ORBIIOPIPv4=1
> 
> You also need to modify your Java runtime environment to include
> gnome-java-bridge.jar in $JRE_HOME/lib/ext  and accessibility.properties
(Continue reading)

Permalink | Reply | 6 comments |
headers
Padraig O'Briain | 1 Nov 2004 14:53
Picon

Re: Java-access-bridge INSTALL Discrepency


Janina Sajka wrote:

>Thanks, Padraig. Unfortunately, I see two typos in the new guidance
>below--at least, I think they're typos:
>
>Padraig O'Briain writes:
>  
>
>>The text in the INSTALL file is wrong. I have updated it in CVS . I have
>>attached the new version to this mail.
>>
>>    
>>
>... snip snip ...
>  
>
>>You may optionally include a java_home environment variable:
>>
>>	./autogen.sh --prefix=/opt/gnome-2.0 --with-java-home=/usr/java/j2sdk1.4.0
>>
>>(2a) If you obtained the java-access-bridge via a tarfile,
>>run "./configure" in this directory with options as above.
>>
>>(3) run make to build gnome-java-access.tar.  You will need 
>>a Java Virtual Machine version 1.4.0 beta4 or higher.  
>>
>>(4) run make install. 
>>
>>(5) before running a Java program with the Java Access Bridge, you
(Continue reading)

Permalink | Reply | 5 comments |
headers
Olaf Schmidt | 8 Nov 2004 11:21
Picon
Favicon

Accessibility <at> freedektop mailing list


Hi!

A new accessibility <at> freedesktop.org mailing list has been created to 
intensify cooperation between several Unix/linux related accessibility 
projects.

http://freedesktop.org/mailman/listinfo/accessibility

The list will focus on developing news interoperable APIs and techniques, 
some of which might later be adopted by the FSG Accessibility Workgroup 
for standardization. The list will also be a place to discuss topics like 
accessibility in the X server etc.

The informal talks leading to the creation of the new mailing list have 
included developers who are also active at GNOME, KDE, SpeechDispatcher, 
BRASS, FreeTTS, ViaVoice, Sphinx, Mozilla, FSG Accessibility Workgroup, 
IBM, Sun Microsystems, SuSE/Novell, and Trolltech.

As a first project, we plan to work on a common driver API for speech 
synthesis and speech recognition engines, meaning that KDE, GNOME, 
SpeechDispatcher, etc. will all bridge to a common low-level driver API.

At a later point, we might have a look at the application side, too, but 
cooperation is far more difficult here.

Olaf

--

-- 
Olaf Schmidt, KDE Accessibility Project
(Continue reading)

Permalink | Reply | 2 comments |
headers
Olaf Schmidt | 8 Nov 2004 18:42
Picon
Favicon

Re: Accessibility <at> freedektop mailing list


[Olaf Schmidt, Montag, 8. November 2004 11:21]
> A new accessibility <at> freedesktop.org mailing list has been created to
> intensify cooperation between several Unix/linux related accessibility
> projects.
>
> http://freedesktop.org/mailman/listinfo/accessibility
>

I just received a note that there seems to be a technical problem with the 
accessibility-request email address. Please use the weblink in the 
confirmation request email until this is solved.

Olaf

--

-- 
Olaf Schmidt, KDE Accessibility Project
KDEAP co-maintainer, maintainer of http://accessibility.kde.org
Permalink | Reply | 0 comments |
headers
Janina Sajka | 10 Nov 2004 14:33

Re: Java-access-bridge INSTALL Discrepency

I'm returning to this email and have expanded the cc's on the email
somewhat. I am trying to be thorough here because I author a HOWTO for
Linux users that's widely read by users who are blind or visually
impaired. So, please bear with my desire for clarity here:

Padraig O'Briain writes:
> 
> 
> Janina Sajka wrote:
> 
> >Thanks, Padraig. Unfortunately, I see two typos in the new guidance
> >below--at least, I think they're typos:
> >
> >Padraig O'Briain writes:
> >  
> >
> >>The text in the INSTALL file is wrong. I have updated it in CVS . I have
> >>attached the new version to this mail.
> >>
> >>    
> >>
> >... snip snip ...
> >  
> >
> >>You may optionally include a java_home environment variable:
> >>
> >>	./autogen.sh --prefix=/opt/gnome-2.0 --with-java-home=/usr/java/j2sdk1.4.0
> >>
> >>(2a) If you obtained the java-access-bridge via a tarfile,
> >>run "./configure" in this directory with options as above.
(Continue reading)

Permalink | Reply | 4 comments |
headers
Padraig O'Briain | 10 Nov 2004 15:18
Picon

Re: Java-access-bridge INSTALL Discrepency

Janina,

I believe that the references to environment variables in the INSTALL
file is shorthand.

I reinstalled my desktop system this morning and this is what I did to
get accessibility working for Java applications.

Note that I do not have JAVA_HOME or JRE_HOME environment variables set.
If I do `which java` I get /usr/bin/java. /usr/bin/java is a link to
/usr/java/bin/java. /usr/java is a link to /usr/jdk/instances/jdk1.5.0.
The GNOME files of interest, i.e. accessibility.properties and
gnome-java-bridge.jar, are in /usr/share/jar/.

su -
cd /usr/jdk/instances/jdk1.5.0/jre/lib
ln -s /usr/share/jar/accessibility.properties .
cd ext
ln -s /usr/share/jar/gnome-java-bridge.jar .

Java applications will now load the java access bridge.

Padraig

Janina Sajka wrote:
> I'm returning to this email and have expanded the cc's on the email
> somewhat. I am trying to be thorough here because I author a HOWTO for
> Linux users that's widely read by users who are blind or visually
> impaired. So, please bear with my desire for clarity here:
>
(Continue reading)

Permalink | Reply | 3 comments |
headers
Bill Haneman | 10 Nov 2004 15:24
Picon

Re: Java-access-bridge INSTALL Discrepency

Hi:

Since $JRE_HOME is not referenced in the configure.in file, I think we
should remove references to it in the README.  Alternatively, it may
make sense to add checks for $JRE_HOME in configure.in, because some
installations may be $JRE_HOME set and $JAVA_HOME unset.  If we do the
latter, then $JRE_HOME should be mentioned in README as an optional
environment variable which is searched for the Java runtime and library
files.

- Bill

On Wed, 2004-11-10 at 14:18, Padraig O'Briain wrote:
> Janina,
> 
> I believe that the references to environment variables in the INSTALL
> file is shorthand.
> 
> I reinstalled my desktop system this morning and this is what I did to
> get accessibility working for Java applications.
> 
> Note that I do not have JAVA_HOME or JRE_HOME environment variables set.
> If I do `which java` I get /usr/bin/java. /usr/bin/java is a link to
> /usr/java/bin/java. /usr/java is a link to /usr/jdk/instances/jdk1.5.0.
> The GNOME files of interest, i.e. accessibility.properties and
> gnome-java-bridge.jar, are in /usr/share/jar/.
> 
> su -
> cd /usr/jdk/instances/jdk1.5.0/jre/lib
> ln -s /usr/share/jar/accessibility.properties .
(Continue reading)

Permalink | Reply | 0 comments |
headers
Kenny Hitt | 11 Nov 2004 20:38

success with gnopernicus 0.8.4 Gnome 2.6 in Debian

Hi.  I recently installed a new Debian system.  I upgraded the box to
unstable.  I installed the Debian packages for Gnome and Gnopernicus.
In Debian, Gnome 2.6 and Gnopernicus 0.8.4 are the latest available.  I
haven't installed any Java support.  Since Debian doesn't allow Java in
it's main distro, I don't believe any Java packages were installed
as dependencys.
I've noticed I have a very stable system. I haven't crashed Gnopernicus
or any gnome app in the over 2 months I've been running it this way.
There are some problems with accessibility, but no problems with
stability.  On my other Debian box which has Sun's JDK installed,
Gnopernicus is very unstable.  That box's Gnome is basically useless.
Does anyone have an idea why a system using only Debian packages is so
stable while a box with Java support isn't?  The box with Java install
is completely stable for my sighted girl friend who doesn't use any
Gnome accessibility features.  That would suggest the stability problems
are part of the accessibility and not a general problem.

One other strange thing is Mozilla access.  the box with Java installed
doesn't have much access to Mozilla.  the box with all Debian packages
will allow me to read web pages using Mozilla-firefox.  The access isn't
perfect, but it is noticably better than anything I've had before.
I thought Java was a requirement for Mozilla access.  Can someone pleas
explain what is going on?

          Kenny
Permalink | Reply | 20 comments |
headers
Peter Korn | 11 Nov 2004 20:50
Picon

Re: [g-a-devel] success with gnopernicus 0.8.4 Gnome 2.6 in Debian

Hi Kenny,

Without a detailed list of the versions of all of the bits that you are 
running, it is difficult to attempt to diagnose anything.  I'm very pleased to 
hear you have a very stable system with Gnopernicus now - the internal stuff 
we're running in Sun is reasonably stable for us.

Java is NOT a requirement for Mozilla access; only for StarOffice and of 
course for Java applications.

Regards,

Peter Korn
Sun Accessibility team

Kenny Hitt wrote:
> Hi.  I recently installed a new Debian system.  I upgraded the box to
> unstable.  I installed the Debian packages for Gnome and Gnopernicus.
> In Debian, Gnome 2.6 and Gnopernicus 0.8.4 are the latest available.  I
> haven't installed any Java support.  Since Debian doesn't allow Java in
> it's main distro, I don't believe any Java packages were installed
> as dependencys.
> I've noticed I have a very stable system. I haven't crashed Gnopernicus
> or any gnome app in the over 2 months I've been running it this way.
> There are some problems with accessibility, but no problems with
> stability.  On my other Debian box which has Sun's JDK installed,
> Gnopernicus is very unstable.  That box's Gnome is basically useless.
> Does anyone have an idea why a system using only Debian packages is so
> stable while a box with Java support isn't?  The box with Java install
> is completely stable for my sighted girl friend who doesn't use any
(Continue reading)

Permalink | Reply | 16 comments |

Gmane