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
On 11/1/06, Willie Walker [EMAIL PROTECTED] 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
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
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 ;-)):
On Mon, 2006-10-16 at 14:20 -0400, Willie Walker wrote:
I'm not sure I understand the question, but you can manually get and set
the key via:
Maybe i'm just stupid, but it seems to me that you first set a_t_support
depending on the version, and then run:
+ a_t_value = gconf_client_get
Sounds fine to me. I know zilch about the gconf stuff, and I'm only
offering some stuff as a starting point. Since you obviously know far
more about it than I do, I think instead of a smart guy (you) exchanging
e-mail with an ignorant guy (me) to provide incremental improvements,
would you be
On Sun, 2006-10-15 at 10:44 +0200, Mark Rosenstand wrote:
(Yeah, some kind of gconf-diff that shows how your settings are
different from the system defaults would be way cool...)
Attached. :)
Regards,
Rob
--
Rob Bradford [EMAIL PROTECTED]
#!/usr/bin/env python
### Copyright (C) 2006
These lines are supposed to say hey, if the key is defined, then use
its value regardless of what the default setting is:
+ a_t_value = gconf_client_get (gconf_client, ACCESSIBILITY_KEY, NULL);
+ if (a_t_value)
+a_t_support = gconf_value_get_bool (a_t_value);
This allows you to disable
On Mon, 2006-10-16 at 07:30 -0400, Willie Walker wrote:
These lines are supposed to say hey, if the key is defined, then use
its value regardless of what the default setting is:
+ a_t_value = gconf_client_get (gconf_client, ACCESSIBILITY_KEY, NULL);
+ if (a_t_value)
+a_t_support =
On Mon, 2006-10-16 at 13:10 +0200, Alexander Larsson wrote:
On Sun, 2006-10-15 at 20:32 -0400, Willie Walker wrote:
I'd say that the best way to do this is like the code for G_DEBUG,
just check gnome version in libgnomeui, and if odd number, enable it
unconditionally. If even, check the
Le dimanche 15 octobre 2006, à 20:32, Willie Walker a écrit :
I'd say that the best way to do this is like the code for G_DEBUG,
just check gnome version in libgnomeui, and if odd number, enable it
unconditionally. If even, check the gconf key.
Sounds good to me. It seems like the right
I'm not sure I understand the question, but you can manually get and set
the key via:
gconftool-2 --get /desktop/gnome/interface/accessibility
gconftool-2 --type bool --set /desktop/gnome/interface/accessibility true
As for determining the GNOME release version, this is already done
further up
On Sun, 2006-10-15 at 02:42 +0200, Sven Herzberg wrote:
Hey Willie,
Am Samstag, den 14.10.2006, 19:18 -0400 schrieb Willie Walker:
As part of the GNOME Boston 2006 Accessibility Summit, and as part of
the larger GNOME testing discussions, we would like to propose that
accessibility is
I'd say that the best way to do this is like the code for G_DEBUG,
just check gnome version in libgnomeui, and if odd number, enable it
unconditionally. If even, check the gconf key.
Sounds good to me. It seems like the right spot to do this might be in
gnome-session/main.c. I submitted an
Will,
Yes.
As we see more and more software consuming the at-spi interfaces (gui
testing tools, screen readers, on-screen keyboards, at-poke, gui event
loggers) it just makes sense to get as much testing coverage as
possible. Let's fix the bugs in the development releases.
cheers,
David
Hey Willie,
Am Samstag, den 14.10.2006, 19:18 -0400 schrieb Willie Walker:
As part of the GNOME Boston 2006 Accessibility Summit, and as part of
the larger GNOME testing discussions, we would like to propose that
accessibility is enabled by default for GNOME development releases.
That is,
On 10/15/06, Sven Herzberg [EMAIL PROTECTED] wrote:
The idea sounds pretty good. I just have one question: If I run a beta
as my first GNOME, the gconf key will be set to TRUE, will it
automatically switch to FALSE once I upgrade to stable GNOME? (Will it
work the other way around?)
I'd say
On Sat, 2006-10-14 at 19:48 -0400, David Bolter wrote:
As we see more and more software consuming the at-spi interfaces (gui
testing tools, screen readers, on-screen keyboards, at-poke, gui event
loggers) it just makes sense to get as much testing coverage as
possible. Let's fix the bugs
18 matches
Mail list logo
