Jay
As for point # 4 regarding the listeners, the java accessibility
framework
already provides event firing on almost every type of component change
you
can think of including focus change, state change, mouse movement, and so
on. These events are what WE4Java monitors to know what data to send to
the
screen reader. Unless you had something else in mind as far as an event
wrapper mechanism, the mechanics already built into the swing
accessibility
architecture do a really good job without developing any custom event
code.
I'm not sure, honestly. Maybe we should talk sometime on skype. It's
possible we're both duplicating each other's work.
For example, have you come up with neat solutions for any of the
following:
1. Issues like Non-accessible code in the NetBeans platform?
2. How do you deal with virtual machine implementations that don't
properly route events through Java, for example, the menus on Mac OS
X.
3. How do you deal with components that popup, but do not actually
fire events, like code completion windows or editor hints?
I'm just curious, as any potential for collaboration is a good thing,
Stefik
__________
View the list's information and change your settings at
//www.freelists.org/list/programmingblind
