Ah, that's different. That'd actually require using Gtk/Qt which we cannot do, the best we can get is to look like them.
What's the problem, licensing, integration or thread-safety (I know QT isn't thread safe)
To be fully accessible we'd need to implement the OLE Accessibility framework and bridge it to AT-SPI or something similar.
I may have a look at that too, it would be useful if QT/GTK could use some of the existing Windows accessibility software.
I was thinking about going on a fund finding mission, or at least trying to find someone who wants to pay for an initial integration, it shouldn't be too hard as most companies are no where near their requirements.
Send instant messages to your online friends http://uk.messenger.yahoo.com
On Sat, 2005-03-12 at 21:00 +0000, Oliver Stieber wrote:
Ah, that's different. That'd actually require using Gtk/Qt which we cannot do, the best we can get is to look like them.
What's the problem, licensing, integration or thread-safety (I know QT isn't thread safe)
Well all those *could* be problems, but the real problem is that the Windows widget toolkit and GTK/Qt are too different, you can't map between them.
I may have a look at that too, it would be useful if QT/GTK could use some of the existing Windows accessibility software.
No, that's not what I meant. Implementing OLE accessibility would mean that Win32 apps on Wine appear to in native tools like at-poke. It wouldn't mean you could use win32 accessibility software to access native apps.
I was thinking about going on a fund finding mission, or at least trying to find someone who wants to pay for an initial integration, it shouldn't be too hard as most companies are no where near their requirements.
Good luck!
thanks -mike
-
Mike Hearn -
Oliver Stieber