Re: GOK



Hi Gunnar and Olaf:

You might checking for at-spi-registryd, the "assistive technology
registry daemon"

ps -elf | grep spi-registryd

If it's not running, then either it isn't getting activated
(you can test this with the bonobo activation client query utility,
activation-client -s "repo_ids.has('IDL:Accessibility/Registry:1.0')"
which should activate the registry and return an IOR string to the
console) or it's crashing right after activation.

If you want to make sure the registry's binary is present on your
system, or if activation if failing, you can search for
$prefix/libexec/at-spi-registryd (where $prefix is the directory into
which you installed GNOME).  If activation fails, perhaps something is
wrong with your bonobo-activation setup?  There should be a file in 
$prefix/lib/bonobo/servers called "Accessibility_Registry.server" which
tells bonobo-activation where to find the registry and what interfaces
it implements, etc.

You can run the at-spi-registryd executable yourself (though it is not
in your $PATH), in a console window, and you may see some diagnostic
output which could give you more clues.  For instance on my system I
would run:
/opt/gnome-2.0/libexec/at-spi-registryd

Then launch GOK and see what happens.

As for your mother's needs: what sorts of input devices do you think may
work for her?  As you probably know, GOK can use either "point and
dwell" (if the mouse pointer enters and remains inside an onscreen-key
'button' it activates that key) or various switch-activated methods (for
instance, buttons start and stop scanning row-by-row and
column-by-column, and make selections).  The first option works well if
she has reasonable pointing ability with perhaps a joystick or
trackball; there is also a head-tracking device from Madentec that costs
about $300 that works for people who can only control head movement, it
tracks a small reflective dot placed on the forehead.

The switch devices are actually mouse-button emulators.  There are
various single-switch buttons available, and a box called XKeys allows
you to plug these relatively inexpensive switches (which are usually
between 3 and 5 inches in diameter) into a little box which makes them
act as mouse buttons.  GOK uses the mouse button events to control the
scanning modes so you can test this with an ordinary mouse.  You may
find that some trackballs have big enough mouse buttons for your mother
to use, or you can always take a soldering iron to a regular mouse and
wire in new buttons :-)  As you know GOK features word prediction and
can grab menus and toolbar control info from an application and add it
to its own UI, which reduces the number of "keystrokes" the user must
input.

Now, as for speech; we don't have a "KMouth"-type type-and-say utility
yet, but gnome-speech provides all the necessary building blocks and it
should only take a few lines of code to create one.  If you want any
pointers in that area please let us know and we can provide some
suggestions.  Basically a simple GTK+ app (whose toolbars and menus will
automatically get picked up by GOK if you have GNOME accessibility
turned on) with a text entry window and two buttons ("say", and "clear",
perhaps) would be enough, and the GTK+ app could call gnome-speech to
obtain a suitable text-to-speech voice and then call 

GNOME_Speech_Speaker_say (text_string_to_speak, &ev);

-best regards and good luck!

Bill

On Fri, 2002-11-15 at 08:08, Gunnar Schmi Dt wrote:
> Hello,
> 
> > [...]
> > It looks to me as though there might be problems with your
> > at-spi-registryd.  Could you please give us more information about your
> > GNOME installation.  Where it came from, what version it is and so on.
> > Could you also tell us how you are starting your GNOME session?
> > [...]
> Like all of the I've installed GNOME from the SuSE 8.1 CDs. I start it from 
> KDM by selecting "GNOME" as the window manager to start. (I do not exactly 
> know what SuSE does when starting GNOME.)
> 
>  As you may not know SuSE 8.1 I give you the version numbers of some of the 
> installed GNOME packages:
> 
> libgnomecanvas-2.0.2-61
> gnome-common-1.2.4-255
> libgnome-2.0.2-60
> gnome-libs-1.4.1.7-105
> libgnomeui-2.0.3-59
> gnome-desktop-2.0.6-60
> gnome-session-2.0.5-60
> bonobo-conf-0.14-450
> libbonobo-2.0.0-165
> libbonoboui-2.0.1-58
> bonobo-1.0.20-167
> gconf2-1.2.1-64
> at-spi-1.0.0-208
> 
> I have put the full output of "rpm -qa" onto http://www.schmi-dt.rpm.txt.
> 
> After starting GNOME the following processes are running:
> 
> gunnars kcshilb:~> ps -ef | grep gunnars
> gunnars   1690  1629  5 07:27 ?        00:00:00 /opt/gnome2/bin/gnome-session
> gunnars   1710     1  0 07:27 ?        00:00:00 /opt/gnome/bin/medusa-idled
> gunnars   1737     1  0 07:27 ?        00:00:00 esd -terminate -nobeeps -as 2 
> -spawnfd 9
> gunnars   1739     1  6 07:27 ?        00:00:00 /opt/gnome2/libexec/gconfd-2 9
> gunnars   1741     1  2 07:27 ?        00:00:00 bonobo-activation-server 
> --ac-activate --ior-output-fd=15
> gunnars   1743     1  0 07:27 ?        00:00:00 gnome-smproxy 
> --sm-config-prefix /.gnome-smproxy-rkhglc/ --sm-client-id 
> 11c0a8ab83000103734141900000014330000
> gunnars   1745     1  4 07:27 ?        00:00:00 gnome-settings-daemon 
> --oaf-activate-iid=OAFIID:GNOME_SettingsDaemon --oaf-ior-fd=10
> gunnars   1748     1  2 07:27 ?        00:00:00 xscreensaver -nosplash
> gunnars   1750     1  4 07:27 ?        00:00:00 metacity --sm-save-file 
> 1037341433-1493-2597548831.ms
> gunnars   1753     1 16 07:27 ?        00:00:01 nautilus --sm-config-prefix 
> /nautilus-jeDGR4/ --sm-client-id 11c0a8ab83000103734142000000014330003 
> --no-default-window
> gunnars   1755     1 13 07:27 ?        00:00:01 gnome-panel --sm-config-prefix 
> /gnome-panel-xAe0z6/ --sm-client-id 11c0a8ab83000103734142000000014330002 
> --profile default
> gunnars   1756  1753  0 07:27 ?        00:00:00 nautilus --sm-config-prefix 
> /nautilus-jeDGR4/ --sm-client-id 11c0a8ab83000103734142000000014330003 
> --no-default-window
> gunnars   1757  1756  0 07:27 ?        00:00:00 nautilus --sm-config-prefix 
> /nautilus-jeDGR4/ --sm-client-id 11c0a8ab83000103734142000000014330003 
> --no-default-window
> gunnars   1758  1756  0 07:27 ?        00:00:00 nautilus --sm-config-prefix 
> /nautilus-jeDGR4/ --sm-client-id 11c0a8ab83000103734142000000014330003 
> --no-default-window
> gunnars   1760     1  5 07:27 ?        00:00:00 
> /opt/gnome2/libexec/mixer_applet2 
> --oaf-activate-iid=OAFIID:GNOME_MixerApplet_Factory --oaf-ior-fd=17
> gunnars   1762     1 19 07:27 ?        00:00:00 gnome-terminal
> gunnars   1763  1762  0 07:27 ?        00:00:00 gnome-pty-helper
> gunnars   1764  1762  2 07:27 pts/0    00:00:00 bash
> gunnars   1769  1764  0 07:27 pts/0    00:00:00 ps -ef
> gunnars   1770  1764  0 07:27 pts/0    00:00:00 grep gunnars
> gunnars kcshilb:~>
> 
> Gunnar Schmi Dt
> 
> > > > I have a problem with starting the Gnome Onscreen Keyboard: It simply
> > > > reports "** ERROR **: Could not locate registry" --- and that's it.
> > > >
> > > > I use SuSE 8.1 with KDE 3.0.4, kernel 2.4.19-4GB, gcc 3.2. [...]
> > > >
> > > > [...] During the investigation I found out that the call
> > > > to "make install" installed the configuration data to the home
> > > > directory of the user "root". I used "gconftool-2 --install-schema-file
> > > > gok.schemas" in order to create the configuration for my standard user.
> > > > However, after I have done this, GOK does also not start.
> > > >
> > > > gunnars kcshilb:~> gok
> > > >
> > > > ** ERROR **: Could not locate registry
> > > > aborting...
> > > > Abgebrochen
> > > > gunnars kcshilb:~> gconftool-2 --all-entries /apps/gok
> > > >  resource_directory =3D /opt/gnome2/share/gok
> > > >  keyboard_directory =3D /opt/gnome2/share/gok
> > > >  access_method =3D directselection
> > > >  access_method_directory =3D /opt/gnome2/share/gok
> > > >  word_complete =3D true
> > > >  dictionary_directory =3D /opt/gnome2/share/gok
> > > >  number_predictions =3D 5
> > > > gunnars kcshilb:~> ls -l /opt/gnome2/share/gok
> > > > insgesamt 124
> > > > -rw-r--r--    1 root     root         1550 2002-11-11 12:04
> > > > alphabet.kbd -rw-r--r--    1 root     root        10086 2002-11-11
> > > > 12:04
> > > > automatic-scanning.xam
> > > > -rw-r--r--    1 root     root        37939 2002-11-11 12:04
> > > > dictionary.txt -rw-r--r--    1 root     root         3618 2002-11-11
> > > > 12:04
> > > > direct-selection.xam-rw-r--r--    1 root     root         3584
> > > > 2002-11-11 12:04 dwell-selection.xam
> > > > -rw-r--r--    1 root     root         5658 2002-11-11 12:04 gok.rc
> > > > -rw-r--r--    1 root     root          332 2002-11-11 12:04
> > > > goksound1.wav -rw-r--r--    1 root     root          332 2002-11-11
> > > > 12:04 goksound2.wav -rw-r--r--    1 root     root         8812
> > > > 2002-11-11 12:04
> > > > inverse-scanning.xam-rw-r--r--    1 root     root          738
> > > > 2002-11-11 12:04 launcher.kbd
> > > > -rw-r--r--    1 root     root         1101 2002-11-11 12:04 main.kbd
> > > > -rw-r--r--    1 root     root          838 2002-11-11 12:04 manage.kbd
> > > > -rw-r--r--    1 root     root        17682 2002-11-11 12:04 qwerty.kbd
> > > > gunnars kcshilb:~>
> > > > [...]
> 
> _______________________________________________
> gnome-accessibility-list mailing list
> gnome-accessibility-list gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]