Re: Enable accessibility by default in development releases?

[Kjartan Maraas <kmaraas broadpark no>]

fre, 11,.11.2005 kl. 12.20 -0500, skrev David Malcolm:
> Currently, a11y is not enabled by default in GNOME, as it has a
> performance cost (CPU and memory usage).
> 
> But that means that there's a huge amount of code that isn't being
> exercised by most testers and developers.
> 
> So here's a (possibly crazy) suggestion: during development releases,
> enable a11y by default, and during stable releases, disable it by
> default.  That way people running jhbuild, GARNOME etc would be running
> all of the a11y code, and any bugs in that layer would be discovered
> more quickly.
> 
I'm all for it. Maybe we can get a11y stuff profiled as well and close
the few performance related bugreports for it along the way too.

Cheers
Kjartan