[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-commits
Subject:    www/areas/accessibility/developer
From:       Olaf Jan Schmidt <olaf () amen-online ! de>
Date:       2003-07-14 20:59:51
[Download RAW message or body]

CVS commit by ojschmidt: 

Some corrections


  M +4 -4      bridge.php   1.5
  M +6 -8      introduction.php   1.2
  M +1 -1      kdea11y.php   1.2


--- www/areas/accessibility/developer/bridge.php  #1.4:1.5
@@ -113,8 +113,8 @@
  that the requirements of AT-SPI to the IPC can easily be emulated on top of D-BUS or DCOP.
 </p><p>
- Changing AT-SPI requires great changes to the AT-SPI registry, ATK, OpenOffice,
- Mozilla and the Java accessibility libraries. This would be far more work than
- dealing with CORBA in an optional KDE library. Alternatively, someone could write
- an external bridge, which would be heavy overhead and even more work.
+ Changing AT-SPI requires great changes to the AT-SPI registry, ATK and the Java accessibility
+ libraries. This would be far more work than dealing with CORBA in an optional KDE library.
+ Alternatively, someone could write an external bridge, which would be heavy overhead and
+ even more work.
 </p>
 

--- www/areas/accessibility/developer/introduction.php  #1.1:1.2
@@ -15,6 +15,6 @@
  <a href="#interfaces">Why Special Interfaces Are Needed</a> |
  <a href="#solutions">Existing Solutions</a> |
- <a href="#obstacles">Obstacles And Advantages Of A Bridging Solution</a> |
- <a name="#apis">Why Native APIs Are Needed</a> ]
+ <a href="#obstacles">Obstacles And Advantages of a Bridging Solution</a> |
+ <a href="#apis">Why Native APIs Are Needed</a> ]
 </div>
 
@@ -79,13 +79,11 @@
 </p>
 
-<h2><a name="obstacles">Obstacles And Advantages Of A Bridging Solution</a></h2>
+<h2><a name="obstacles">Obstacles And Advantages of a Bridging Solution</a></h2>
 <p>
  From a KDE perspective, a bridge between Qt and AT-SPI has two problems and one huge
  benefit. The first problem are dependencies, as the AT-SPI registry currently
- requires GTK2+. Fortunately, the GNOME developers
- <a href="http://lists.kde.org/?l=kde-accessibility&m=105670778517807&w=2">have offered</a>
- to get rid of this dependency, so the only dependencies would be glib, ORBIT2, ATK
- and libbonobo. These would not be dependencies for KDE itself, but only for running
- assistive technologies.
+ requires GTK2+. It should be possible to reduce these dependencies to glib and ORBIT2,
+ but this might perhaps require rewriting large parts of it. These would not be dependencies
+ for KDE itself, but only for running assistive technologies.
 </p><p>
  A second problem is the need to use CORBA in assistive technologies.

--- www/areas/accessibility/developer/kdea11y.php  #1.1:1.2
@@ -52,5 +52,5 @@
  Trolltech to contain all the functionality needed to make GUI elements fully
  accessible. Once the next Qt version has been released, KDE can start to write
- QAccessibleInterface objects for those KDE GUI elements that need accessibility
+ QAccessibleInterface objects for those KDE GUI elements that need customized accessibility
  implementations.
 </p><p>


[prev in list] [next in list] [prev in thread] [next in thread]