Hi all, Since we now have more than one toolkit other than GTK making use of atk for accessibility, I think its time we revisit the discussion about a location for the atk bridge shared object, i.e other than the GTK module directory. From skimming through the mail from this list, this was previously discussed, without a concensus reached. Perhaps if a proposal is offered, it could then be improved upon/discussed further, to help reacha concensus much sooner, and thereby be implemented ASAP.
I am still learning about the finer details of atk, so please forgive me if my proposal is somewhat lacking in its assessment and consideration of all the pieces in the puzzle. So far as I understand, this is not a complicated issue, therefore it should be relatively simple to solve. * We still use a shared object, in a similar form to what we have now, except the object doesn't bare any resemblance to gtk in terms of method names. * The shared object is placed in $libdir/atk, and called atk-bridge.$platform_shared_object_extension * The libatk API is extended to provide methods for locating and managing the bridge. * A new GTK module is created that wraps libatk to load the atk-bridge shared object for the currently running app. Suggestions, criticisms etc, most welcome. As stated, I may have missed something, so if I have, please point it out. Luke _______________________________________________ gnome-accessibility-devel mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
