Re: [g-a-devel] Bug 362457 - RFE to enable accessibility in unstable releases of GNOME (libgnome)

[Willie Walker <William Walker Sun COM>]

Hi Henrik:

I believe the answer is more along the lines of 'a'.  If a user has not
set the accessibility property, then the default value for odd versions
of GNOME will be to enable accessibility.  If a user has set the
property, then their preference will be used.  

Note that the only potential source of confusion here will be that
accessibility will be disabled by default for the even releases of
GNOME.  Thus, a naive user using odd releases of GNOME might be
surprised when accessibility is disabled when they upgrade to an even
release.

Note that accessibility friendly distributions such as Ubuntu, however,
probably could choose to just always keep accessibility enabled in the
default schema.

Will

On Mon, 2006-11-27 at 12:55 +0100, Henrik Nilsen Omma wrote:
> Willie Walker wrote:
> > FYI...this took some effort and some good teamwork, but accessibility is
> > now enabled in GNOME development releases by default.  Yeah!
> >
> >   http://bugzilla.gnome.org/show_bug.cgi?id=362457
> >   
> 
> That's great! More testing is good :)
> 
> I think I understand how this will work, but let me ask a few questions 
> just to be sure.
> 
> A default schema setting is used. This does either:
> (a) turns AT on for anyone running 2.17 who has *not* made an explicit 
> choice on that themselves, or
> (b) turns AT on for anyone installing or creating a new user with 2.17
> 
> (please excuse my lack of understanding of how schemas work)
> 
> 
> If (b) is the case:
> 
> * then people upgrading from Edgy to a Feisty test version would not 
> have AT switched on (which is fine, we also see lots of fresh installs 
> so there would still be plenty of testing)
> * and how do we back the change out again towards the end of the testing 
> period? Just removing the patch or letting gnome go to 2.18 won't do it 
> because people's gconf keys will already be set
> 
> Also if someone who needs the AT features installs the testing version 
> they could risk having AT disappear on them at some point in the 
> process. Also not a big problem, because if you are using a test version 
> you can expect odd things to happen. Would there be a way for them to 
> prevent this though if they set the gconf key explicitly?
> 
> 
> Henrik
> _______________________________________________
> Gnome-accessibility-devel mailing list
> Gnome-accessibility-devel gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel