From: Anthony Liguori <aliguori@us.ibm.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Stefan Weil <sw@weilnetz.de>, Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org, Alex Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [PATCH 0/8] Add GTK UI to enable basic accessibility (v2)
Date: Mon, 27 Feb 2012 08:39:03 -0600 [thread overview]
Message-ID: <4F4B9587.8060706@us.ibm.com> (raw)
In-Reply-To: <4F4B9223.70803@redhat.com>
On 02/27/2012 08:24 AM, Kevin Wolf wrote:
> Am 27.02.2012 00:46, schrieb Anthony Liguori:
>> I realize UIs are the third rail of QEMU development, but over the years I've
>> gotten a lot of feedback from users about our UI. I think everyone struggles
>> with the SDL interface and its lack of discoverability but it's worse than I
>> think most people realize for users that rely on accessibility tools.
>>
>> The two pieces of feedback I've gotten the most re: accessibility are the lack
>> of QEMU's enablement for screen readers and the lack of configurable
>> accelerators.
>>
>> Since we render our own terminal using a fixed sized font, we don't respect
>> system font settings which means we ignore if the user has configured large
>> print.
>>
>> We also don't integrate at all with screen readers which means that for blind
>> users, the virtual consoles may as well not even exist.
>>
>> We also don't allow any type of configuration of accelerators. For users with
>> limited dexterity (this is actually more common than you would think), they may
>> use an input device that only inputs one key at a time. Holding down two keys
>> at once is not possible for these users.
>>
>> These are solved problems though and while we could reinvent all of this
>> ourselves with SDL, we would be crazy if we did. Modern toolkits, like GTK,
>> solve these problems.
>>
>> By using GTK, we can leverage VteTerminal for screen reader integration and font
>> configuration. We can also use GTK's accelerator support to make accelerators
>> configurable (Gnome provides a global accelerator configuration interface).
>>
>> I'm not attempting to make a pretty desktop virtualization UI. Maybe we'll go
>> there eventually but that's not what this series is about.
>>
>> This is just attempting to use a richer toolkit such that we can enable basic
>> accessibility support. As a consequence, the UI is much more usable even for a
>> user without accessibility requirements so it's a win-win.
>>
>> Also available at:
>>
>> https://github.com/aliguori/qemu/tree/gtk.2
>>
>> ---
>> v1 -> v2
>> - Add internationalization support. I don't actually speak any other languages
>> so I added a placeholder for a German translation. This can be tested with
>> LANGUAGE=de_DE.UTF-8 qemu-system-x86_64
>
> Looks like I need to 'make install' before I can use the translations? I
> don't have any qemu version installed into the system, but always run it
> from to build directory (I would only confuse the different trees if
> something was installed). Shouldn't it be possible that qemu finds the
> right files just like it does with the BIOS etc.?
It's a little harder because of the way gettext works. You can only have a
single search path AFAICT.
We could add a --with-localedir= to configure and then rearrange the po/
structure. Then you would do something like:
./configure --with-localedir=$(pwd)/po
And it would use translations from your build directory.
>> - Fixed the terminal size for VteTerminal widgets. I think the behavior makes
>> sense now.
>> - Fixed lots of issues raised in review comments (see individual patches)
>>
>> Known Issues:
>> - I saw the X crash once. I think it has to do with widget sizes. I need to
>> work harder to reproduce.
>> - I've not recreated the reported memory leak yet.
>> - I haven't added backwards compatibility code for older VteTerminal widgets
>> yet.
>
> - F10 still activates the menu (same for Alt-F/V)
This is expected behavior although Grab on Hover will cause it to behave like
SDL does.
F10/Alt-F/V are menu accelerators and we need to allow menu accelerators for
things like Ctrl-Alt-2 to work.
More importantly, it should be possible to navigate the GUI without a mouse
(this is an accessibility requirement). Without supporting Alt-F, there's no
way to navigate the menu from the keyboard.
That said, we probably do want to add a Send Key menu for sending key sequences
that are used as accelerators.
Regards,
Anthony Liguo
>
> Kevin
>
next prev parent reply other threads:[~2012-02-27 14:40 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-26 23:46 [Qemu-devel] [PATCH 0/8] Add GTK UI to enable basic accessibility (v2) Anthony Liguori
2012-02-26 23:46 ` [Qemu-devel] [PATCH 1/8] console: allow VCs to be overridden by UI Anthony Liguori
2012-02-26 23:46 ` [Qemu-devel] [PATCH 2/8] chr: check to see if front end has registered a read function Anthony Liguori
2012-02-26 23:46 ` [Qemu-devel] [PATCH 3/8] ui: add basic GTK gui (v2) Anthony Liguori
2012-02-26 23:46 ` [Qemu-devel] [PATCH 4/8] gtk: add virtual console support (v2) Anthony Liguori
2012-02-27 10:45 ` Kevin Wolf
2012-02-26 23:46 ` [Qemu-devel] [PATCH 5/8] gtk: add support for input grabbing Anthony Liguori
2012-02-26 23:46 ` [Qemu-devel] [PATCH 6/8] gtk: add support for screen scaling and full screen (v2) Anthony Liguori
2012-02-27 20:10 ` Stefan Weil
2012-02-27 22:01 ` Anthony Liguori
2012-02-28 14:18 ` Kevin Wolf
2012-02-26 23:46 ` [Qemu-devel] [PATCH 7/8] gtk: add translation support Anthony Liguori
2012-02-27 8:32 ` Paolo Bonzini
2012-02-27 13:11 ` Anthony Liguori
2012-02-28 15:10 ` Kevin Wolf
2012-02-27 22:09 ` Stefan Weil
2012-02-26 23:46 ` [Qemu-devel] [PATCH 8/8] gtk: make default UI Anthony Liguori
2012-02-27 7:23 ` [Qemu-devel] [PATCH 0/8] Add GTK UI to enable basic accessibility (v2) malc
2012-02-27 8:21 ` Jan Kiszka
2012-02-27 13:10 ` Anthony Liguori
2012-02-27 13:26 ` Jan Kiszka
2012-02-27 13:33 ` Anthony Liguori
2012-02-27 13:42 ` Jan Kiszka
2012-02-27 13:50 ` Anthony Liguori
2012-02-27 13:54 ` Jan Kiszka
2012-02-27 16:39 ` Gerd Hoffmann
2012-02-27 16:44 ` Anthony Liguori
2012-02-27 16:54 ` Gerd Hoffmann
2012-02-27 14:24 ` Kevin Wolf
2012-02-27 14:39 ` Anthony Liguori [this message]
2012-02-27 15:03 ` Kevin Wolf
2012-03-11 17:29 ` Stefan Weil
2012-03-11 18:24 ` François Revol
2012-03-11 18:47 ` Stefan Weil
2012-03-12 2:31 ` Anthony Liguori
2012-03-12 16:39 ` François Revol
2012-03-12 17:13 ` Anthony Liguori
2012-03-12 2:30 ` Anthony Liguori
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F4B9587.8060706@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=agraf@suse.de \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).