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 ;-)): >> >> http://bugzilla.gnome.org/show_bug.cgi?id=362457 >> >> Thanks! >> >> Will >> >> On Sat, 2006-10-14 at 19:18 -0400, Willie Walker wrote: >> >>> Hi All: >>> >>> 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, make the /desktop/gnome/interface/accessibility gconf setting >>> be True by default for the "odd" (e.g., 2.17.x) releases. >>> >>> A couple of the reasons for doing this include the following: >>> >>> o The accessibility infrastructure will be used as part of the larger >>> testing work. Having accessibility enabled by default will make it a >>> little easier to set up and use the testing facilities. A lower barrier >>> to entry means more people might be encouraged to test. ;-) >>> >>> o We need broader use and coverage of the accessibility infrastructure. >>> Having accessibility enabled by default will help provide this. >>> >>> When we proposed this idea at the afternoon summary to all of the GNOME >>> Boston 2006 attendees, the response seemed to be fairly positive. Jeff >>> suggested posting a proposal to this list to see if we can get the ball >>> rolling. >>> >>> Thoughts? >>> >>> Will >>> >>> >>> ___ >>> desktop-devel-list mailing list >>> desktop-devel-list@gnome.org >>> http://mail.gnome.org/mailman/listinfo/desktop-devel-list >>> > > ___ > desktop-devel-list mailing list > desktop-devel-list@gnome.org > http://mail.gnome.org/mailman/listinfo/desktop-devel-list > ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Proposal to enable accessibility by default for GNOME development releases
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 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 Index: configure.in === RCS file: /cvs/gnome/libgnome/configure.in,v retrieving revision 1.246 diff -u -r1.246 configure.in --- configure.in 4 Sep 2006 14:30:45 - 1.246 +++ configure.in 1 Nov 2006 16:00:58 - @@ -191,6 +191,15 @@ AC_CHECK_LIB(popt, poptStrippedArgv,, AC_MSG_ERROR([popt 1.5 or newer is required to build libgnome. You can download the latest version from ftp://ftp.rpm.org/pub/rpm/dist/rpm-4.0.x/])) +LIBGNOME_MINOR_VERSION=libgnome_minor_version +if test $(( $(echo $LIBGNOME_MINOR_VERSION) %2)) == "1"; then + A11Y_ENABLED=true +else + A11Y_ENABLED=false +fi + +AC_SUBST(A11Y_ENABLED) + AC_CONFIG_FILES([ Makefile libgnome-zip @@ -198,6 +207,7 @@ libgnome/Makefile monikers/Makefile schemas/Makefile +schemas/desktop_gnome_interface.schemas.in gnome-data/Makefile libgnome/libgnome-2.0.pc libgnome/libgnome-2.0-uninstalled.pc diff -u desktop_gnome_interface.schemas.in.in.orig desktop_gnome_interface.schemas.in.in --- schemas/desktop_gnome_interface.schemas.in.in.orig 31 Aug 2006 21:47:20 - +++ schemas/desktop_gnome_interface.schemas.in.in 1 Nov 2006 16:00:58 - @@ -6,7 +6,7 @@ /desktop/gnome/interface/accessibility gnome bool - false + @A11Y_ENABLED@ Enable Accessibility Whether Applications should have accessibility support ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Proposal to enable accessibility by default for GNOME development releases
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. 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 ;-)): > > http://bugzilla.gnome.org/show_bug.cgi?id=362457 > > Thanks! > > Will > > On Sat, 2006-10-14 at 19:18 -0400, Willie Walker wrote: > > Hi All: > > > > 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, make the /desktop/gnome/interface/accessibility gconf setting > > be True by default for the "odd" (e.g., 2.17.x) releases. > > > > A couple of the reasons for doing this include the following: > > > > o The accessibility infrastructure will be used as part of the larger > > testing work. Having accessibility enabled by default will make it a > > little easier to set up and use the testing facilities. A lower barrier > > to entry means more people might be encouraged to test. ;-) > > > > o We need broader use and coverage of the accessibility infrastructure. > > Having accessibility enabled by default will help provide this. > > > > When we proposed this idea at the afternoon summary to all of the GNOME > > Boston 2006 attendees, the response seemed to be fairly positive. Jeff > > suggested posting a proposal to this list to see if we can get the ball > > rolling. > > > > Thoughts? > > > > Will > > > > > > ___ > > desktop-devel-list mailing list > > desktop-devel-list@gnome.org > > http://mail.gnome.org/mailman/listinfo/desktop-devel-list ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Proposal to enable accessibility by default for GNOME development releases
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 ;-)): http://bugzilla.gnome.org/show_bug.cgi?id=362457 Thanks! Will On Sat, 2006-10-14 at 19:18 -0400, Willie Walker wrote: > Hi All: > > 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, make the /desktop/gnome/interface/accessibility gconf setting > be True by default for the "odd" (e.g., 2.17.x) releases. > > A couple of the reasons for doing this include the following: > > o The accessibility infrastructure will be used as part of the larger > testing work. Having accessibility enabled by default will make it a > little easier to set up and use the testing facilities. A lower barrier > to entry means more people might be encouraged to test. ;-) > > o We need broader use and coverage of the accessibility infrastructure. > Having accessibility enabled by default will help provide this. > > When we proposed this idea at the afternoon summary to all of the GNOME > Boston 2006 attendees, the response seemed to be fairly positive. Jeff > suggested posting a proposal to this list to see if we can get the ball > rolling. > > Thoughts? > > Will > > > ___ > desktop-devel-list mailing list > desktop-devel-list@gnome.org > http://mail.gnome.org/mailman/listinfo/desktop-devel-list ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Proposal to enable accessibility by default for GNOME development releases
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 Robert Bradford <[EMAIL PROTECTED]>
### This program is free software; you can redistribute it and/or modify
### it under the terms of the GNU General Public License as published by
### the Free Software Foundation; either version 2 of the License, or
### (at your option) any later version.
### This program is distributed in the hope that it will be useful,
### but WITHOUT ANY WARRANTY; without even the implied warranty of
### MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
### GNU General Public License for more details.
### You should have received a copy of the GNU General Public License
### along with this program; if not, write to the Free Software
### Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
###
### Recursively searches from a path looking for gconf keys that either have
### different values to the schema or those that don't have a matching schema.
###
### Usage:
### ./gconf-diff
### If no start path is given then it starts in /
###
import gconf, sys
# Get the default gconf client
client = gconf.client_get_default()
def do_entries(path):
# Get all the entries in the directory
entries = client.all_entries(path)
# If the directory is non-empty
if entries != ():
for entry in entries:
# Need the key to be useful
key = entry.key
# Get the default
default = client.get_default_from_schema(key)
# If no schema default == None
if default == None:
print "Key without schema: %s" % key
else:
# Get the values of both our the default and our version.
# These are converted to strings for comparison
value = entry.get_value().to_string()
defvalue = default.to_string()
if (value != defvalue):
print "Key with different value: %s - %s (default: %s)" % (key, value,
defvalue)
def do_directory(path):
# Now we deal with the contents of the directordy
do_entries(path)
# Recurse
directories = client.all_dirs(path)
for directory in directories:
# Don't do the /schemas directory
if (directory != "/schemas"):
do_directory(directory)
if (len(sys.argv) == 2):
do_directory(sys.argv[1])
else:
do_directory("/")
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Proposal to enable accessibility by default for GNOME development releases
Actually - after a cup of coffee, I think I now understand better what you're requesting. Just one method call change, I think. When I did the earlier patches, I was looking for parameters to the gconf_client_get call to allow me to do this and was surprised not to find them. Somehow I missed the gconf_client_get_without_default variant. New patch submitted: http://bugzilla.gnome.org/show_bug.cgi?id=362457 We'll eventually get there. The main positive thing is that the community seems to be in overall support of enabling a11y in development releases. The bad thing is that you have someone ignorant in the driver seat (me), but he's at least listening to directions. Thanks! Will On Tue, 2006-10-17 at 07:52 -0400, Willie Walker wrote: > 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 able to work up a patch that does the right thing? It > might save us a lot of time. > > Thanks! > > Will > > On Tue, 2006-10-17 at 08:48 +0200, Alexander Larsson wrote: > > 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 (gconf_client, ACCESSIBILITY_KEY, NULL); > > + if (a_t_value) > > +a_t_support = gconf_value_get_bool (a_t_value); > > > > Which, if the key is unset by the user, will always return the schema > > default value for the key, thereby always overwriting the previous > > version. > > > > Shouldn't you be using gconf_client_get_without_default() here? > > > > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > Alexander LarssonRed Hat, Inc > >[EMAIL PROTECTED][EMAIL PROTECTED] > > He's a maverick crooked shaman from the 'hood. She's a ditzy hip-hop > > journalist with the soul of a mighty warrior. They fight crime! > > > > ___ > desktop-devel-list mailing list > desktop-devel-list@gnome.org > http://mail.gnome.org/mailman/listinfo/desktop-devel-list ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Proposal to enable accessibility by default for GNOME development releases
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 able to work up a patch that does the right thing? It might save us a lot of time. Thanks! Will On Tue, 2006-10-17 at 08:48 +0200, Alexander Larsson wrote: > 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 (gconf_client, ACCESSIBILITY_KEY, NULL); > + if (a_t_value) > +a_t_support = gconf_value_get_bool (a_t_value); > > Which, if the key is unset by the user, will always return the schema > default value for the key, thereby always overwriting the previous > version. > > Shouldn't you be using gconf_client_get_without_default() here? > > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Alexander LarssonRed Hat, Inc >[EMAIL PROTECTED][EMAIL PROTECTED] > He's a maverick crooked shaman from the 'hood. She's a ditzy hip-hop > journalist with the soul of a mighty warrior. They fight crime! > ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Proposal to enable accessibility by default for GNOME development releases
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 (gconf_client, ACCESSIBILITY_KEY, NULL); + if (a_t_value) +a_t_support = gconf_value_get_bool (a_t_value); Which, if the key is unset by the user, will always return the schema default value for the key, thereby always overwriting the previous version. Shouldn't you be using gconf_client_get_without_default() here? =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Alexander LarssonRed Hat, Inc [EMAIL PROTECTED][EMAIL PROTECTED] He's a maverick crooked shaman from the 'hood. She's a ditzy hip-hop journalist with the soul of a mighty warrior. They fight crime! ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Proposal to enable accessibility by default for GNOME development releases
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 in the same file for which the patch was generated
(gnome-session/main.c, which you can view at
http://cvs.gnome.org/viewcvs/*checkout*/gnome-session/gnome-session/main.c).
The patched version looks like this:
versions = g_strsplit (VERSION, ".", 3);
if (versions && versions [0] && versions [1])
{
int major;
major = atoi (versions [1]);
if ((major % 2) != 0 && is_later_than_date_of_doom ())
{
putenv ("G_DEBUG=fatal_criticals");
g_log_set_always_fatal (G_LOG_LEVEL_CRITICAL);
/* Also enable accessibility by default in unstable releases
* of GNOME.
*/
a_t_support = TRUE;
}
}
Hope this helps,
Will
On Mon, 2006-10-16 at 14:09 +0200, Alexander Larsson wrote:
> 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 = gconf_value_get_bool (a_t_value);
> >
> > This allows you to disable a11y by setting the key to False. I hope
> > this addresses the concern you raised.
>
> And how exactly do we map the current version (stable or unstable) to
> this key?
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Alexander LarssonRed Hat, Inc
>[EMAIL PROTECTED][EMAIL PROTECTED]
> He's a globe-trotting small-town sorceror living undercover at Ringling Bros.
> Circus. She's a manipulative insomniac magician's assistant operating on the
> wrong side of the law. They fight crime!
>
> ___
> desktop-devel-list mailing list
> desktop-devel-list@gnome.org
> http://mail.gnome.org/mailman/listinfo/desktop-devel-list
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Proposal to enable accessibility by default for GNOME development releases
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 spot to do this might be in > gnome-session/main.c. I submitted an enhancement request and potential > patch to gnome-session for this, though I've been unable to autogen > gnome-session in order to see if it works (let alone compiles): I'm probably the one who broke gnome-session and I didn't get some public shame, so... here, let me slap myself :-) I'll fix it today. Vincent -- Les gens heureux ne sont pas pressés. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Proposal to enable accessibility by default for GNOME development releases
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 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 enhancement request and potential > > patch to gnome-session for this, though I've been unable to autogen > > gnome-session in order to see if it works (let alone compiles): > > > > http://bugzilla.gnome.org/show_bug.cgi?id=362457 > > I'm not sure about that. That makes it pretty hard to disable it, say if > you want to test something without a11y. I imagine this need to test without a11y is based on the idea that the a11y framework will introduce new bugs which aren't necessarily in your code, and would not otherwise be there. The goal with enabling a11y by default is so that we can fix all of these bugs, and eventually just get rid of the need for a gconf key and ugly hack that loads GTK+ modules to enable a11y support, and have it Just Work (TM) all the time. Note that this also is not to enable sticky keys/etc... but only to enable the loading of the a11y GTK+ modules by default. Your question is one we face now for the critical-warnings-are-fatal hack. How does one test without forcing the app to crash on critical warnings? One must muck with their environment, and unset the variables. You could also do this for the a11y hack. Most all of the issues that keep a11y from being enabled by default in the first place, would be fixed, were people to enable it and try to use their machines with it enabled by default. It merely lacks testing and use in several areas. -- dobey ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Proposal to enable accessibility by default for GNOME development releases
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 = gconf_value_get_bool (a_t_value); > > This allows you to disable a11y by setting the key to False. I hope > this addresses the concern you raised. And how exactly do we map the current version (stable or unstable) to this key? =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Alexander LarssonRed Hat, Inc [EMAIL PROTECTED][EMAIL PROTECTED] He's a globe-trotting small-town sorceror living undercover at Ringling Bros. Circus. She's a manipulative insomniac magician's assistant operating on the wrong side of the law. They fight crime! ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Proposal to enable accessibility by default for GNOME development releases
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 a11y by setting the key to False. I hope this addresses the concern you raised. Will 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 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 enhancement request and potential > > patch to gnome-session for this, though I've been unable to autogen > > gnome-session in order to see if it works (let alone compiles): > > > > http://bugzilla.gnome.org/show_bug.cgi?id=362457 > > I'm not sure about that. That makes it pretty hard to disable it, say if > you want to test something without a11y. > > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Alexander LarssonRed Hat, Inc >[EMAIL PROTECTED][EMAIL PROTECTED] > He's a deeply religious overambitious romance novelist fleeing from a secret > government programme. She's a violent out-of-work mechanic in the witness > protection program. They fight crime! > ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Proposal to enable accessibility by default for GNOME development releases
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 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 enhancement request and potential > patch to gnome-session for this, though I've been unable to autogen > gnome-session in order to see if it works (let alone compiles): > > http://bugzilla.gnome.org/show_bug.cgi?id=362457 I'm not sure about that. That makes it pretty hard to disable it, say if you want to test something without a11y. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Alexander LarssonRed Hat, Inc [EMAIL PROTECTED][EMAIL PROTECTED] He's a deeply religious overambitious romance novelist fleeing from a secret government programme. She's a violent out-of-work mechanic in the witness protection program. They fight crime! ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Proposal to enable accessibility by default for GNOME development releases
> 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 enhancement request and potential patch to gnome-session for this, though I've been unable to autogen gnome-session in order to see if it works (let alone compiles): http://bugzilla.gnome.org/show_bug.cgi?id=362457 Thanks! Will ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Proposal to enable accessibility by default for GNOME development releases
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 enabled by default for GNOME development releases. > > That is, make the /desktop/gnome/interface/accessibility gconf setting > > be True by default for the "odd" (e.g., 2.17.x) releases. > > 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?) Unless you change it, it will be updated. And since we're talking about a boolean value, you wouldn't even notice if it didn't, except 2.19 would have it disabled. (Yeah, some kind of gconf-diff that shows how your settings are different from the system defaults would be way cool...) ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Proposal to enable accessibility by default for GNOME development releases
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 in the development releases. I agree this is a good idea. I once tried to write a tool that used the SPI framework, but got discouraged because things I needed like the Terminal behaved strangely (I filed this and discovered it was a known issue). These issues would only exist for mere days if the people who know how to fix them are experiencing them. --d -- Davyd Madeley http://www.davyd.id.au/ 08B0 341A 0B9B 08BB 2118 C060 2EDD BB4F 5191 6CDA ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Proposal to enable accessibility by default for GNOME development releases
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 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. Salu2 ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Proposal to enable accessibility by default for GNOME development releases
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, make the /desktop/gnome/interface/accessibility gconf setting > be True by default for the "odd" (e.g., 2.17.x) releases. 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?) Regards, Sven ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Proposal to enable accessibility by default for GNOME development releases
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 Willie Walker wrote: > Hi All: > > 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, make the /desktop/gnome/interface/accessibility gconf setting > be True by default for the "odd" (e.g., 2.17.x) releases. > > A couple of the reasons for doing this include the following: > > o The accessibility infrastructure will be used as part of the larger > testing work. Having accessibility enabled by default will make it a > little easier to set up and use the testing facilities. A lower barrier > to entry means more people might be encouraged to test. ;-) > > o We need broader use and coverage of the accessibility infrastructure. > Having accessibility enabled by default will help provide this. > > When we proposed this idea at the afternoon summary to all of the GNOME > Boston 2006 attendees, the response seemed to be fairly positive. Jeff > suggested posting a proposal to this list to see if we can get the ball > rolling. > > Thoughts? > > Will > > > ___ > desktop-devel-list mailing list > desktop-devel-list@gnome.org > http://mail.gnome.org/mailman/listinfo/desktop-devel-list > ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Proposal to enable accessibility by default for GNOME development releases
Hi All: 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, make the /desktop/gnome/interface/accessibility gconf setting be True by default for the "odd" (e.g., 2.17.x) releases. A couple of the reasons for doing this include the following: o The accessibility infrastructure will be used as part of the larger testing work. Having accessibility enabled by default will make it a little easier to set up and use the testing facilities. A lower barrier to entry means more people might be encouraged to test. ;-) o We need broader use and coverage of the accessibility infrastructure. Having accessibility enabled by default will help provide this. When we proposed this idea at the afternoon summary to all of the GNOME Boston 2006 attendees, the response seemed to be fairly positive. Jeff suggested posting a proposal to this list to see if we can get the ball rolling. Thoughts? Will ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
