From: Gonglei <arei.gonglei@huawei.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "Huangweidong (C)" <weidong.huang@huawei.com>,
"lcapitulino@redhat.com" <lcapitulino@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Huangpeng (Peter)" <peter.huangpeng@huawei.com>
Subject: Re: [Qemu-devel] [RFC PATCH v2 0/6] Support to change VNC keyboard layout dynamically
Date: Thu, 4 Dec 2014 10:32:40 +0800 [thread overview]
Message-ID: <547FC7C8.6050304@huawei.com> (raw)
In-Reply-To: <1417608638.14168.49.camel@nilsson.home.kraxel.org>
On 2014/12/3 20:10, Gerd Hoffmann wrote:
> Hi,
>
>> Hi, Daniel
>> Actually, my team had received the requirement of changing VNC keyboard
>> layout dynamically on the scenario of Desktop Cloud. The clientele just use
>> the simplest tight vnc client, but not GTK-VNC etc. I think we should support
>> this scenario, isn't it ?
>
> It boils down to doing the keysym -> scancode translation on the server
> side (tightvnc client, qemu vnc server needs -k) or on the client side
> (anything gtk-vnc based, such as virt-viewer / remote-viewer or vinagre
> (gnome vnc viewer)).
>
> The big advantage of doing it on the client side (then send the
> scancodes using the scancode extension as mentioned by Daniel) is that
> it works without any manual configuration, and you can even have two vnc
> clients with different local keymaps connected at the same time and
> things are still working properly.
>
I see, great thanks for your explanation, Gerd :)
> In case the client can't do the translation qemu will fallback to do it
> on the server side. It's not the recommended way to operate though.
>
Hum.. Now, I encountered this situation that the common clienteles just use
tightvnc client, but want to change keymap dynamically. As you say,
the only way address this scenario is doing it on the server side. So,
do you think this patch series make sense and consider to accept it
in upstream? Thanks!
Regards,
-Gonglei
next prev parent reply other threads:[~2014-12-04 2:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 6:55 [Qemu-devel] [RFC PATCH v2 0/6] Support to change VNC keyboard layout dynamically arei.gonglei
2014-12-03 6:55 ` [Qemu-devel] [RFC PATCH v2 1/6] vnc: introduce vnc_display_kbd_layout function arei.gonglei
2014-12-03 6:55 ` [Qemu-devel] [RFC PATCH v2 2/6] vnc: add a new QMP command for changing keyboard layout arei.gonglei
2014-12-03 6:55 ` [Qemu-devel] [RFC PATCH v2 3/6] vnc: HMP change-vnc-kbd-layout wrapper arei.gonglei
2014-12-03 6:55 ` [Qemu-devel] [RFC PATCH v2 4/6] qapi-schema: fix typo about change-vnc-password arei.gonglei
2014-12-03 6:55 ` [Qemu-devel] [RFC PATCH v2 5/6] keymaps: correct keymaps.c following Qemu coding style arei.gonglei
2014-12-03 6:55 ` [Qemu-devel] [RFC PATCH v2 6/6] keymaps: convert fprintf to qerror_report arei.gonglei
2014-12-03 9:38 ` [Qemu-devel] [RFC PATCH v2 0/6] Support to change VNC keyboard layout dynamically Daniel P. Berrange
2014-12-03 9:50 ` Gonglei
2014-12-03 9:54 ` Daniel P. Berrange
2014-12-03 10:04 ` Gonglei
2014-12-03 12:10 ` Gerd Hoffmann
2014-12-04 2:32 ` Gonglei [this message]
2014-12-04 8:47 ` Gerd Hoffmann
2014-12-04 9:46 ` Gonglei
2014-12-04 9:53 ` Daniel P. Berrange
2014-12-04 10:18 ` Gonglei
2014-12-04 12:07 ` Gonglei
2014-12-04 12:10 ` Daniel P. Berrange
2014-12-04 12:16 ` Gonglei
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=547FC7C8.6050304@huawei.com \
--to=arei.gonglei@huawei.com \
--cc=kraxel@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=peter.huangpeng@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=weidong.huang@huawei.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.