In terms of the a11y tab and feature, I wouldn't tie it in as suggested
on that page. I may have it default to one setting or the other based
on whether or not the a11y feature is enabled in Gnome, but not
restrict it to using that setting. Users may want to employ some or
all of the mouse a11y features without enabling the entire a11y
subsystem. Kirk Denis Washington wrote: On Wed, 2007-10-31 at 13:44 +0100, Rodrigo Moya wrote:On Tue, 2007-10-30 at 19:20 +0100, Vincent Untz wrote:Le samedi 13 octobre 2007, à 14:25 +0200, Francesco Fumanti a écrit :Hello, During the accessibility summit last weekend, an new accessibility application called Mousetweaks was presented: http://mail.gnome.org/archives/gnome-accessibility-devel/2007-October/msg00022.html In order to make it more gnome conform, its user interface will probably have to be reviewed. I prepared a wiki page for that purpose which should provide most relevant informations: http://live.gnome.org/mousetweaks/usabilityI don't know if control center people are aware of this effort, so I'm cc'ing them: all this has some impact on the current capplets.we are discussing about an 'input devices' capplet, so not sure how this fits in. Maybe we should look at how mousetweaks could be integrated into this new capplet, although it would add lots of settings just for the mouse. Any other comments?I have made a mockup that integrates Mousetweaks settings into the mouse capplet: http://ultimum-projekt.de/mockups/mouse.html I hope I haven't forgotten everything. Comments? Regards, Denis _______________________________________________ Usability mailing list Usability gnome org http://mail.gnome.org/mailman/listinfo/usability |