Re: [Qemu-devel] [PATCH 0/6] Add GTK UI to enable basic accessibility

[Anthony Liguori <anthony@codemonkey.ws>]

On 02/25/2012 11:02 AM, Stefan Weil wrote:
> Am 20.02.2012 00:44, schrieb Anthony Liguori:
>> Hi,
>>
>> 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.
>
> This first version of the new GTK UI still shares some problems with
> the SDL UI and adds new ones:
>
> It's quite common for the VGA code to set a very small size (e.g. 1 x 1 pixel)
> during boot. MIPS Malta does (if no VGA module like cirrusfb is loaded,
> it will never set a different size), and even the 386 / x86_64 emulation
> has a (very short) time were the display size is unusually small.

It doesn't.  It cycles through modes 640x480, 720x400, then VGA modes.  It never 
resizes to 1x1.

But..  GTK should handle this better.  Even if the drawing area sets the size to 
1x1, the window should maintain a size at least large enough to render the menu 
bar properly.

> This results in a very small window size which is only limited by the display
> manager.
> Usually it is so small that any user interaction with the window becomes difficult.
>
> The GDK UI increases the problem because it also resizes the monitor, serial and
> all other text consoles. On Ubuntu, I get a Malta serial console with 7 characters
> in 5 rows, and the serial output also wraps after 7 characters.

I'm going to fix the terminal widths to something reasonable so that shouldn't 
be a problem anymore.

> Zooming changes the number of rows and lines, not the size of the characters
> in all text consoles.

I'm going to disable zooming when VGA is not the current tab.


> There is also a new kind of QEMU crash:
>
> The program '<unknown>' received an X Window System error.
> This probably reflects a bug in the program.
> The error was 'BadAlloc (insufficient resources for operation)'.
> (Details: serial 28914 error_code 11 request_code 53 minor_code 0)
> (Note to programmers: normally, X errors are reported asynchronously;
> that is, you will receive the error a while after causing it.
> To debug your program, run it with the --sync command line
> option to change this behavior. You can then get a meaningful
> backtrace from your debugger if you break on the gdk_x_error() function.)
>
> I just got it while writing this mail when I wanted to check some facts.
>
> Program '<unknown>' is not user friendly (crashing never is, but when it
> crashes, at least the error message should be good :-)).
> The bug also occurred a second time when I started MIPS Malta
> (when the Linux kernel loaded module cirrusfb), so it seems to be
> reproducible.

Sounds like malloc failure.

Regards,

Anthony Liguori

>
> Regards,
> Stefan Weil
>
>