| QDBusBridge | |||
| |||
| Platforms: | X11 | ||
| Qt version: | >= 4.3.1 | ||
| License: | GPL | ||
| Depends on: | QtDBus | ||
QDBusBridge blogs | |||
Subversion:
| |||
The D-Bus Accessibility Bridge exposes the accessible interfaces through D-Bus. The interfaces are close to IAccessible2 and AT-SPI.
To build the bridge, check out the sources, make sure to have Qt 4.3.1 or higher installed and run:
/path/to/qt/bin/qmake make
The bridge is copied into Qt's plugin directory. If that directory is not writable, either build as root user or edit the DESTDIR line in qdbusbridge.pro.
Once the bridge is built, you have to set the QT_ACCESSIBILITY environment variable:
export QT_ACCESSIBILITY=1
Now, you can launch any Qt application. If you have a debug build, you should see the line initializing D-BUS accessible bridge printed to your console on application startup.
You can use IAPoke or any other D-Bus introspection tool to introspect the accessibility data.
To summarize my achievement at Akademy:
[Argument: a{sv} {”a” = [Variant(int): 1], “b” = [Variant(QByteArray): {99}], “c” = [Variant(QString): “b”], “d” = [Variant(uint): 42], “date” = [Variant: [Argument: (iii) 1977, 1, 1]], “datetime” = [Variant: [Argument: ((iii)(iiii)i) [Argument: (iii) 0, 0, 0],[Argument: (iiii) 8, 59, 31, 0], 0]], “dtlist” = [Variant: [Argument: a((iii)(iiii)i) {[Argument: ((iii)(iiii)i) [Argument: […]
The Qt D-Bus accessibility bridge is now at labs.trolltech.com. You can find the bridge, an introspection tool and a port of Dasher that shows how to manipulate text edits through D-Bus.
If you find a widget that doesn’t expose enough information or behaves badly, please let us know.