Re: About making public gtk accessibility headers

[Matthias Clasen <matthias clasen gmail com>]

On Tue, Aug 7, 2012 at 5:02 AM, Emmanuele Bassi <ebassi gmail com> wrote:
> hi;
>
> On 7 August 2012 09:49, Piñeiro <apinheiro igalia com> wrote:
>> This thread didn't take too much attention, but I assume that it is due
>> the post-GUADEC back-to-home trip. Anyway, I want to add some extra
>> information here.
>
>> So the options are:
>>   a) Make gtk accessibility headers public (my preferred option)
>
> this would obviously be the preferred option, from the perspective of
> third party developers; it obviously adds constraints on the whole
> accessibility API, but if it removes the need to create hacks inside
> gtk+ to allow third party code to make custom widgets accessible then
> it's a reasonable burden.
>

The way things are currently set up, 3rd party a11y implementations
have to directly implement atk interfaces, the gtk implementations are
private and not subclassable from the outside. Can you explain why
that is a problem ?