summaryrefslogtreecommitdiff
path: root/gtk/a11y/gtkscrolledwindowaccessible.c
Commit message (Collapse)AuthorAgeFilesLines
* Remove ATKEmmanuele Bassi2020-07-261-173/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | To build a better world sometimes means having to tear the old one down. -- Alexander Pierce, "Captain America: The Winter Soldier" ATK served us well for nearly 20 years, but the world has changed, and GTK has changed with it. Now ATK is mostly a hindrance towards improving the accessibility stack: - it maps to a very specific implementation, AT-SPI, which is Linux and Unix specific - it requires implementing the same functionality in three different layers of the stack: AT-SPI, ATK, and GTK - only GTK uses it; every other Linux and Unix toolkit and application talks to AT-SPI directly, including assistive technologies Sadly, we cannot incrementally port GTK to a new accessibility stack; since ATK insulates us entirely from the underlying implementation, we cannot replace it piecemeal. Instead, we're going to remove everything and then incrementally build on a clean slate: - add an "accessible" interface, implemented by GTK objects directly, which describe the accessible role and state changes for every UI element - add an "assistive technology context" to proxy a native accessibility API, and assign it to every widget - implement the AT context depending on the platform For more information, see: https://gitlab.gnome.org/GNOME/gtk/-/issues/2833
* Replace "gint" with "int"Benjamin Otte2020-07-251-4/+4
|
* Replace most remaining uses of container apiMatthias Clasen2020-05-111-33/+16
| | | | These are all on GtkBox or enumerating children.
* scrolledwindow: Derive from GtkWidgetMatthias Clasen2020-05-041-5/+2
| | | | | | | | | | | | We want to remove GtkBin and GtkContainer as they don't provide much useful functionality anymore. This requires us to move get_request_mode and compute_expand down. We have to implement GtkBuildable, in order to keep the <child> element in ui files working for aspect frames. See #2681
* a11y/ScrolledWin|IconView: Connect signals safelyJuan Pablo Ugarte2018-04-221-6/+6
| | | | | | | | Use g_signal_connect_data() instead of g_signal_connect_object() to make sure the callback gets disconnected when the data object is destroyed. This avoids problems in garbage-collected bindings. https://bugzilla.gnome.org/show_bug.cgi?id=789215
* CosmeticsMatthias Clasen2012-12-271-1/+1
| | | | Replace GAIL in top comments by 'GTK+ - accessibility implementations'.
* Make accessible implementations publicMatthias Clasen2012-12-271-4/+4
| | | | | | | | | | | | | | This commit exposes the get_type() functions and standard headers for accessible implementations. This makes it possible to derive from the GTK accessible implementations without GType magic tricks. This is necessary, because we require the a11y type hierarchy to be parallel to the widget type hierarchy. So, if you derive a widget and need to adjust its a11y implementation, you have to be able to derive its accessible implementation. This commit probably exposes more than is absolutely necessary, it also exposes accessibles of widgets that are unlikely candidates for deriving from.
* Change FSF AddressJavier Jardón2012-02-271-3/+1
|
* Use canonical namesMatthias Clasen2011-07-171-2/+2
| | | | Use canonical names for both signals and properties.
* Avoid unnecessary includesMatthias Clasen2011-07-101-2/+1
| | | | | Including string.h makes the compiler complain about parameters and variables called index, which is not nice.
* Reduce the number of unwanted exportsMatthias Clasen2011-07-091-4/+5
| | | | | _-prefix most of the get_type functions in a11y/. There are still some more symbols left.
* Convert GailContainer to GtkContainerAccessibleMatthias Clasen2011-07-051-1/+1
|
* Emit the same changed_children details as everybody elseMatthias Clasen2011-07-051-1/+1
| | | | ...if any of this was documented...
* Convert GailScrolledWindow to GtkScrolledWindowAccessibleMatthias Clasen2011-07-051-0/+195