Re: Keyboard a11y tab

[Rodrigo Moya <rodrigo gnome-db org>]

On Sat, 2007-11-10 at 11:18 +0100, Denis Washington wrote:
> On Fri, 2007-11-09 at 22:10 +0100, Francesco Fumanti wrote:
> > At 9:27 PM +0100 11/9/07, Denis Washington wrote:
> > >Hi,
> > >
> > >As discussed in a previous thread, plans are under way to merge the
> > >keyboard and keyboard a11y capplets into a single. For those who haven't
> > >followed that discussion, here is the initial mockup I made:
> > >
> > >http://ultimum-projekt.de/mockups/keyboard.html
> > >
> > >Some of the smaller issues (like the a11y button still being there ;))
> > >are already fixed in my local .glade file. However, there is still one
> > >big problem with the mockup: the accessibility options are organized
> > >pretty badly. Putting all options into one tab makes the dialog much too
> > >high, so I put all "beep if..."-like options into an external
> > >"Notifications" window. This is very suboptimal, so we need another way
> > >to display these options. One option we were thinking about is putting
> > >the different a11y features into expanders; expanding one of them would
> > >lead to all other ones to be collapsed, which keeps the maximum height
> > >of the capplet window fairly small. Here is a mockup showing the idea:
> > >
> > >http://ultimum-projekt.de/mockups/expanders.png
> > >
> > >Comments and additional ideas to organize the a11y options are very
> > >welcome.
> > 
> > Maybe that using buttons to open subwindows might also be a way to 
> > go, especially if there are many option.
> > 
> > Firefox does it for example (Exceptions..., Show Cookies...):
> > http://www.mozilla.org/support/firefox/options#privacy
> > 
> > But this is perhaps what you intended by external "Notifications" window.
> > 
> > Cheers
> > 
> > Francesco
> > 
> > PS: We had a similar problem with mousetweaks, that in fact is 
> > nothing else than the mouse accessibility. It currently uses an 
> > expander to hide a few popup menus:
> > http://live.gnome.org/Mousetweaks/Usability
> >   (currently the last picture of the page)
> 
> It's right that having external windows for less frequently used options
> is a good solution, that's why I took that path in my first mockup. But
> the separation between the options that are in the tab and those in the
> external window should make sense somehow, and I think separating the
> beeping settings from the actual keyboard a11y features is a bit of an
> artificial separation. But maybe we can find something to put in an
> external window that makes more sense. Suggestions are welcome.
> 
as you said, windows for less frequently used options (or extended
options) is ok, but for this dialog, it seems wrong. And I really like
the expanders solution, and, AFAIK, doesn't break any HIG rule, so I
guess it is the way to go
-- 
Rodrigo Moya <rodrigo gnome-db org>