Re: Proposal to enable accessibility by default for GNOME development releases

Willie Walker wrote:
> OK - I'll answer my own question - this approach doesn't seem to do what
> we want.  In testing and testing with this, the problem is that some
> assistive technologies depend upon the existence and value of the key
> itself: if it's not enabled, they let the user know and then enable it.
> I embarassingly know this now because that's what Orca does, and I'm
> pretty sure it's what Gnopernicus does.
>   

GOK does it too :-P

David

> So....
>
> It seems as though the right thing to do is enable accessibility in the
> default schema for development releases.  Anyone have a clue for how to
> do this?
>
> Will
>
> On Fri, 2006-10-27 at 11:12 -0400, Willie Walker wrote:
>   
>> Hi All:
>>
>> This has festered for a little bit without further comment, so I'd like
>> to poke it one more time to try to get this in for the GNOME 2.17.2
>> tarballs.  Please speak up if you disagree and/or don't like the
>> proposed patch (and you have a constructive alternative solution ):
>>

Re: Proposal to enable accessibility by default for GNOME development releases

On 11/1/06, Willie Walker <William.Walker <at> sun.com> wrote:
>
> So....
>
> It seems as though the right thing to do is enable accessibility in the
> default schema for development releases.  Anyone have a clue for how to
> do this?

We can use a autoconf variable on the schema file and expand it
depending on minor version of libgnome (the packaging owning that
schema).

We would need to rename:
schemas/desktop_gnome_interface.schemas.in
to:
schemas/desktop_gnome_interface.schemas.in.in

and apply the attached patch to do the auto* magic voodoo and use the
variable in the schema file.

Salu2

_______________________________________________
desktop-devel-list mailing list
desktop-devel-list <at> gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list