From: Piñeiro <[email protected]> > > To use ATSPI-dbus as underlying inter-process communication pr= > otocol, I made some change to CALLY: > > = > > > static gboolean > > _a11y_invoke_module (const gchar *libname, > > const gchar *dirname, > > gboolean init) > > { > > ..... > > if (strcmp ((char*)libname, "libcally-1.0") =3D=3D 0) { > > if (init) > > method =3D "gnome_accessibility_module_init"; > > else > > method =3D "gnome_accessibility_module_shutdown"; > > = > > > } > > # make a soft link /usr/local/lib/gtk-2.0/modules/libatk-bridge.so to= > /usr/local/lib/gtk-2.0/modules/libspiatk.so > > # libspiatk is implemented as gtk module > > Somewhat hacky ;), but a good way to get working what you > want. Probably the best way to solve that should modify this example > in order to specify a CORBA or DBUS environment. I guess that this > libspiatk.so is what I called previously atk-adaptor.
BTW: I have just modified the examples in order to use the correct at-spi bridge. By default it uses the bonobo one, but you can use the option --with-dbus, in order to try to use the atk-adaptor that came with at-spi-dbus, and use the proper initialization method hook. So you can execute this examples right now in this way: $ ./cally-atkcomponent-example --with-dbus Anyway, as I said before, take into account that this is just a example of how and which modules are required to be loaded, but in a final environment this would be different. BR === API ([email protected]) -- To unsubscribe send a mail to [email protected]
