Revision as of 20:25, 20 January 2012 (view source)Frederik (talk | contribs) (→Running KDE/Qt applications)← Older edit Revision as of 20:27, 20 January 2012 (view source) Frederik (talk | contribs) (→For More Information)Newer edit → Line 62: Line 62: == For More Information == == For More Information == − * [http://labs.qt.nokia.com/category/labs/accessibility/|Qt labs accessibility blog posts]+* [http://labs.qt.nokia.com/category/labs/accessibility/ Qt labs accessibility blog posts] − * [https://mail.kde.org/mailman/listinfo/kde-accessibility|KDE Accessibility mailing list]+* [https://mail.kde.org/mailman/listinfo/kde-accessibility KDE Accessibility mailing list] − * [http://userbase.kde.org/Accessibility|Accessibility information for KDE users]+* [http://userbase.kde.org/Accessibility Accessibility information for KDE users] − * [http://userbase.kde.org/Accessibility/Application_Overview|Accessibility status of KDE applications]+* [http://userbase.kde.org/Accessibility/Application_Overview Accessibility status of KDE applications] Revision as of 20:27, 20 January 2012 Contents 1 Prerequisits 2 Packages 3 Getting the Latest Code 3.1 Building Qt in your home directory 3.2 Bridge plugin 3.3 Running KDE/Qt applications 4 Status 4.1 Qt 4.8.0 4.2 Qt 4.8.1 4.3 Open issues 5 For More Information Prerequisits * Working at-spi 2 (DBus at-spi) * Either build Qt 4.8 yourself (see below) or find distribution packages. Packages For opensuse there is a package * https://build.opensuse.org/package/show?package=qt-at-spi&project=KDE%3AQt Ubuntu ships an outdated version of the plugin in 11.10 which will crash. Expect a better experience in 12.4. Getting the Latest Code Building Qt in your home directory Only needed when you want to test the latest or your distribution does not have Qt 4.8 packages yet. If you want to build Qt in you home directory, follow these instructions, otherwise skip to the next section. git clone git://gitorious.org/qt/qt.git ~/qt4 cd ~/qt4 git checkout 4.8 ./configure -confirm-license -opensource -no-phonon -debug -no-webkit -fast make -j2 You do not have to make install. The configure options build without Phonon which avoids some problems with KDE applications that ship their own Phonon. After building Qt, you need to export a few variables so that it will be found by applications. export QTDIR="~/qt4" export LD_LIBRARY_PATH=$QTDIR/lib:$LD_LIBRARY_PATH export PATH=$QTDIR/bin:$PATH export QT_ACCESSIBILITY=1 Bridge plugin This is the plugin that makes Qt communicate with AT-SPI via DBus. Once you have Qt 4.8, building this plugin is easy. git clone git://gitorious.org/qt-at-spi/qt-at-spi.git cd qt-at-spi qmake make make install You might need to use qmake-qt4 or qmake-4 if you have qmake default to the Qt 3 version. When building with system Qt, you'll have to use sudo to make install. Running KDE/Qt applications Before starting an application you will have to set the environment variables as mentioned above if you build your own Qt. Otherwise just set: export QT_ACCESSIBILITY=1 Then start the application in the same terminal. Status Please report problems you encounter on the [[email protected]]. Qt 4.8.0 * The basics should work, Orca reads focused widgets * Many text editing widgets do not updated properly when editing or selecting text Qt 4.8.1 You can grab the 4.8 branch from gitorious. * Better support in text editing widgets Open issues For More Information Qt labs accessibility blog posts KDE Accessibility mailing list Accessibility information for KDE users Accessibility status of KDE applications Retrieved from "https://userbase.kde.org/index.php?title=Accessibility/Getting_Started&oldid=230023" Content is available under Creative Commons License SA 4.0 unless otherwise noted.