After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 649471 - Study if AtkSocket/AtkPlug should be interfaces
Study if AtkSocket/AtkPlug should be interfaces
Status: RESOLVED OBSOLETE
Product: atk
Classification: Platform
Component: atk
unspecified
Other Linux
: Normal normal
: ---
Assigned To: ATK maintainer(s)
ATK maintainer(s)
Depends on:
Blocks: 638537
 
 
Reported: 2011-05-05 16:00 UTC by Alejandro Piñeiro Iglesias (IRC: infapi00)
Modified: 2021-06-10 11:27 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Alejandro Piñeiro Iglesias (IRC: infapi00) 2011-05-05 16:00:25 UTC
Right now AtkSocket and AtkPlug are direct AtkObject subclasses.

But it would be good to debate if it has more sense to have them as interfaces.

A practical example:

These days, Mario was creating a basic C example for atksocket/atkplug (souce here [1]).

He needed to redefine the factory for a custom Gtk widget, in order to provide the implementations of AtkSocket/AtkPlug to the accessible hierarchy.

But, as AtkSocket/AtkPlug are AtkObject subclasses, this new object can't be a GtkAccessible subclass. That means that most of the accessible hierarchy would be GtkAccessible subclases, but in the "bridge" part, it wouldn't.

This is not a really big issue, as it is working fine, but means that some of the common things implemented on GtkAccessible (base object management) would be required to be re-implemented on this custom accessible object.

This also applies to AtkGObjectAccessible (ie: used at clutter).


[1] https://gitorious.org/atksocket-atkplug-example
Comment 1 André Klapper 2011-06-23 22:06:53 UTC
[Mass-reassigning open atk bug reports for better trackability as requested in https://bugzilla.gnome.org/show_bug.cgi?id=653179 .
PLEASE NOTE:
If you have watched the previous assignee of this bug report as a workaround for actually getting notified of changes in atk bugs, you yourself will now have to add atk-maint@gnome.bugs to your watchlist at the bottom of https://bugzilla.gnome.org/userprefs.cgi?tab=email to keep watching atk bug reports in GNOME Bugzilla.
Sorry for the noise: Feel free to filter for this comment in order to mass-delete the triggered bugmail.]
Comment 2 André Klapper 2021-06-10 11:27:54 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version of atk, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a ticket at
  https://gitlab.gnome.org/GNOME/atk/-/issues/

Thank you for your understanding and your help.