[Kde-accessibility] OpenOffice and KDE4 Accessiibilty [was: Orca/KDE Integration]

[Éric Bischoff]

Le Mercredi 6 Septembre 2006 19:44, Olaf Jan Schmidt a écrit :
> Hi Bill!
>
> The Qt integration of OpenOffice aims to make OpenOffice blend in nicely
> with KDE. Of course it makes sense for the integration code to also support
> accessibility features.
>
> Is the Java accessibility bridge independent of the widget style that is
> used in OpenOffice, i.e. does it run both with the Gtk and the Qt
> integration code? If this is the case, then I agree that extra work would
> be totally unnecessary here. Otherwise I see no reason to discourage the
> KDE integration developers from considering accessibility in their code -
> even if OpenOffice could use Gtk as an accessibility fallback for KDE in
> the short term.

Hi Olaf,


As a KDE user I hear "Gtk" and "Java" with fear. They might do their job very 
well, but Gtk makes me install one zillion libraries and bloats my machine's 
hard disk and memory, and Java makes me enter the problems of installing a 
virtual machine, and for sure will perform more slowly than compiled code.

If you add to that that Gtk looks awful graphically (from my point of view), 
is coded in a braindead way (pure C with callbacks, or worse, GObjects), that 
Java does not look better graphically and is most of the time proprietary, 
you'll understand why I resent relying on such technologies.

So yes, we agree that we should avoid duplicating efforts and yes, these can 
be short-term fallbacks. But if a feature can be gotten from Qt, I definitely 
prefer that solution. Even if it means coding efforts...

In such cases, if people really want to share efforts, the solution of a 
common library (common to Gnome, KDE, OpenOffice.org etc.), with no Java in 
it, is usually better.

Sorry in advance if I offended someone and/or missed the point.



-- 
La monoculture informatique fragilise le système d'information, elle est aussi 
toxique pour les données de l'entreprise. (Guy Brand)