Re: [g-a-devel] Coming to grips with the state of a11y in gtk

On 02/17/2011 11:22 AM, Piñeiro wrote:
> You are proposing to forget this "proxy" approach on the accessibility
> support. As far as I understand you are proposing to implement the ATK
> interfaces directly on GTK, so instead of having a GTK widget and his
> accessible equivalent, just having a GTK widget implementing the
> proper ATK interfaces, right?
> I already talked about that in the past (ie [1][2]), but summarizing
> the reasons to avoid that:

Turning the Atk classes into interfaces doesn't mean that each
accessible object has to correspond to a *pre-existing* GObject. In the
cases where now you create MyFlyWeightWhateverAccessible or
WebCoreSomethingAccessible as a subclass of AtkObject, in the future
you'd create them as subclasses of GObject, implementing the AtkObject
interface. A tiny bit more boilerplate code, but other than that it
would be just like it is now.

-- Dan

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]