Piñeiro,
Thank you so much for quick answer. My expected test process is
1. Boot moblin to Desktop
2. Set GTK_MODULES environment= cally:spiatk
3. Launch clutter application we'd like test
4. Run pyatspi based test script to talk with our target application
Is above test process reasonable? What do you think?
Thanks
WangJing
-----Original Message-----
From: Piñeiro [mailto:[email protected]]
Sent: 2009年10月13日 22:14
To: Wang, Jing J
Cc: Wan, Shuang; [email protected]
Subject: Re: [clutter] Re: CALLY over ATSPI-dbus
From: "Wang, Jing J" <[email protected]>
> Piñeiro,
> Thanks for your help. I just tried the example --with-dbus, and it
> works fine.
> Next, another problem which may block Clutter GUI Auto Testing is How
> to load Cally and atk adaptor module without apps modification, just as the
> case of gtk application by --gtk-module to load external module.
Yes, this is a know issue, check this bugs [1][2].
One option, although somewhat hackish, is keep using GTK_MODULES, and
just keep installing the cally module in the gtk directory (as says
[1]), and keep using GTK_MODULES. In some environments I used that,
but it is clear that it is a hack-short-term solution. Something like:
GTK_MODULES=cally:atk-bridge (with bonobo)
GTK_MODULES=cally:spiatk (with DBUS)
Although for the last one, I still need to fix this
add_global_event_listener problem.
> I heard you plan to integrate cally into Clutter, really?
Hmm, I think that I don't understand you. Right now Cally is in the
o-hand repository, like other clutter add-on (clutter-gst, etc).
If you are talking about the run-time, Cally is as integrated with
Clutter as GAIL is integrated with Gtk+. This have the advantage that
you can load the a11y support only if you require that.
You mean that you would like a deeper integration?
BR
[1] http://bugzilla.o-hand.com/show_bug.cgi?id=1737
[2] http://bugzilla.o-hand.com/show_bug.cgi?id=1738
===
API ([email protected])
