Re: [orca-list] orca, java access bridge and java
- From: Michael Whapples <mwhapples aim com>
- To: Willie Walker <William Walker Sun COM>
- Cc: orca-list gnome org
- Subject: Re: [orca-list] orca, java access bridge and java
- Date: Wed, 14 May 2008 21:33:20 +0100
Hello,
Unfortunately I don't have any knowledge of corba, orbit or PyOrbit
internals, but I have got skills in both java and python. Depending on
how much there is to learn about corba and orbit I may be able to do
something to help. So would I be right in thinking, from what you said,
that loggers associated with corba and orbit would be one source of
information of interest for resolving this problem.
Regarding the key bug, I will see what has changed between orca 2.20.x
and orca 2.22.0 in the script you mentioned, as it was between the above
versions I noticed this particular bug occurring.
Michael Whapples
On Wed, 2008-05-14 at 09:28 -0400, Willie Walker wrote:
Hi Michael:
If you have Java CORBA internals, ORBit internals, and potentially
PyORBit internals knowledge, we could use your expertise in tracking
down the intermittent failures we are running into.
For the keyboard problem, we still have your bug logged as
http://bugzilla.gnome.org/show_bug.cgi?id=525650, which also points to
http://bugzilla.gnome.org/show_bug.cgi?id=318615. I believe the main
problem is that Java has its own idea of keycodes which differs from the
keycodes used by the X Windows System. So, funky keycode translation is
needed.
The funky keycode translation is currently being done in
src/orca/scripts/toolkits/J2SE-access-bridge.py:consumesKeyboardEvent.
It basically takes the keysym of the event and passes it to X asking for
the keycode. This is not a very good solution. I believe the real
translation should be done in the Java Access Bridge and not in Orca. I
did something like this for a Java-based VNC client I wrote several
years back and need to dig up the code and propose a patch for the
bridge. It's basically a huge ugly table.
However, in my mind, the intermittent failure we're getting is far worse
of a problem and I'm spending my efforts trying to get some traction
with that problem.
Will
Michael Whapples wrote:
As I use java regularly, what would be the best way for me to help out
with trying to track down some of the problems in the gnome java access
bridge? What might be worth increasing the logging level for and what
should I keep to minimal logging?
I have encountered the problems with some controls not behaving as they
should (sometimes text fields not accepting certain key inputs, and even
sometimes orca not speaking or brailling anything when tabbing onto a
control).
There still seems to be the bug I reported that orca uses some character
keys for orca stuff when in java applications (eg. = (equals) key (the
equals on the main keyboard, next to the backspace) is reported (in
learn mode) and behaves as (when not in learn mode) "script information
key), so making it impossible to enter an = sign in text fields). There
are other keys which seem wrongly assigned like this.
Michael Whapples
On Tue, 2008-05-13 at 08:13 -0400, Willie Walker wrote:
Hi Sergio:
There is a bigger problem happening somewhere in the scope of the Java
Access Bridge for GNOME, which differs from the Java Access Bridge for
Windows. This problem can expose symptoms such as some controls being
intermittently accessible, and sometimes just not spoken at all. We're
actively looking at this problem right now, and have made it a goal to
have them resolved by GNOME 2.24 this fall. We don't understand the
problem fully at this point, however, so we cannot guarantee we will
meet this goal. But, we are trying very hard.
Will
1. On java control panel, it's hard to navigate between tabs. I have
to do
the following to navigate: press right down arrow and then space bar,
and
sometimes it doesn't work.
2. On advanced tab of java control panel, It's impossible to read the
tree
view that is displayed. This tree view is very important because it has
security options and browser plugin configurations.
3. I've made a project for a course on faculty, which one class extends
JApplet. I'm unable to read its components.
Is it possible to do anything to solve these problems?
If I'm not wrong, some members of orca team are connected to Sun
Microsystems.
Even if these problems were not part of your scope, is it possible to
contact people that can solve them?
Even if they are not orca bugs, they are critical problems related to
accessibility.
Note: on Microsoft windows, I'm not able to read the tree view on
advanced
tab of java control panel, but I'm able to navigate between the tabs
and I'm
able to read components of classes wich extend JApllet.
Thanks for the attention taken reading this message
Best regards
Srgio Neves
_______________________________________________
Orca-list mailing list
Orca-list gnome org
http://mail.gnome.org/mailman/listinfo/orca-list
Visit http://live.gnome.org/Orca for more information on Orca
_______________________________________________
Orca-list mailing list
Orca-list gnome org
http://mail.gnome.org/mailman/listinfo/orca-list
Visit http://live.gnome.org/Orca for more information on Orca
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]