Re: Enable accessibility by default in development releases?

Just a note - one of our RE engineers Derek, ran some benchmark tests with A11Y on and off:

DR >> I've done some testing with the following...

o Gnome Terminal - Launch and Cat a big file
o Gedit - Launch and load a file
o GtkPerf - iterate thru' gtk test suite.
o Evolution - Launch and Switch to Calender view

Doing 'cat' of a big file in gnome-terminal was the only area where a
significant difference was seen. Approx 45 secs with A11Y ON, and 42.4
secs with A11Y Off.

All other areas looked at above were not significantly different
comparing A11Y On Vs A11Y Off.
So looks good for just turning on the A11Y setting. Now of course this is not looking at enabling and running any of the AT technologies :)


The opt-in is to run:
>>>gconftool-2 --set --type bool /desktop/gnome/interface/accessibility 
The opt-out is to run:
>>>gconftool-2 --set --type bool /desktop/gnome/interface/accessibility 

Federico Mena Quintero wrote:
On Fri, 2005-11-11 at 12:20 -0500, David Malcolm wrote:

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.

Let's do it.

On a few conditions:

- You will write a short tutorial of how to write profiling scripts with

- You will write a little bunch of Dogtail scripts that will help us
profile particularly slow operations (opening the panel menu, doing
stuff in Evolution)

- Sun will write the dtrace scripts to figure out why/how enabling a11y
is a performance problem for the desktop:  a11y does a lot of IPC, and
profiling that is hard unless you have something like dtrace.

All agreed? :)


desktop-devel-list mailing list
desktop-devel-list gnome org

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]