ActiveState recently released the Tkx module on CPAN; Tkx works in a
similar fashion to Python's Tkinter or the existing Tcl::Tk module. Tkx
provides a clean interface into scripting Tk from Perl, and should
support MSAA version 1 at least. Tkx also allows you to use themed Tk
widgets; an example of this could be seen in the Gui interfaces of our
own PDK product.
http://search.cpan.org/~gaas/Tkx-1.02/Tkx.pm
cheers, JeffG
Veli-Pekka Tätilä wrote:
Hi list,
The recent post about GTK on Win32 got me thinking of using that library
in Perl applications intended for Win32. I'd like to do a GUI in perl
but such that it is accessible to WIndows screen reader programs. That's
because I have to use one myself.
While the Win32::GUI package does work, it's still a bit early and
experimental. In particular, I haven't found out a way to load dialog
resources and have found that some window metrics appear to be mising.
TK, on the other hand, is well documented but many of their "standard"
controls are not accessible out of the box. Neither using NArrator nor
with any of the big three readers as far as I know. I've only tried TK
sample apps with Dolphin Supernova 6.x betas, though. Something as
fundamental as a push button doesn't look like a button to the screen
reader and keybord usage is slightly different, too.
So if someone is using GTK2 on WIn32, does that mean the accessibility
support inherent in GTK2 will migrate to Windows via Microsoft Active
accessibility (MSAA)? I suppose not. Most of my experiences about Win32
ported GTK2 apps have been rather negative. I'm not sure if it's just
the Win32 port or the use of custom controls in graphically intensive
apps like Dia.
By the way, even if GTK2 uses MSAA on Windows I reckon the support could
still vary widely. Most readers seem to rely on screen interception and
WIn32 hooks as the primary means of "data mining" with only limited MSAA
support. So, how Windows like the non-native GTK2 widgets appear is down
to the MSAA implementation in a particular reader. If the widgets were
native, however, they would have a familiar MSAA representation in
addition to supporting system-wide Win32 hooks well.
As a case study, the latest Visual Studio betas use MSAA to expose most
of the info on screen. However, current readers, at least on default
settings, cannot make too much sense of the form designer, which I find
a bit ironic considering that it's an MS app and an MS standard. But
that is an OT:ish quibble, anyway.
Any thoughts appreciated.
_______________________________________________
Perl-Win32-Users mailing list
[email protected]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
