From: "Daniel P. Berrange" <berrange@redhat.com>
To: Gonglei <arei.gonglei@huawei.com>
Cc: "kraxel@redhat.com" <kraxel@redhat.com>,
"lcapitulino@redhat.com" <lcapitulino@redhat.com>,
"Huangweidong (C)" <weidong.huang@huawei.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: Wed, 3 Dec 2014 09:54:22 +0000 [thread overview]
Message-ID: <20141203095422.GD10160@redhat.com> (raw)
In-Reply-To: <547EDD01.7050608@huawei.com>
On Wed, Dec 03, 2014 at 05:50:57PM +0800, Gonglei wrote:
> On 2014/12/3 17:38, Daniel P. Berrange wrote:
>
> > On Wed, Dec 03, 2014 at 02:55:40PM +0800, arei.gonglei@huawei.com wrote:
> >> From: Gonglei <arei.gonglei@huawei.com>
> >>
> >> A bonus of this feature is that supporting different
> >> people (in different countries) using defferent keyboard
> >> to connect the same guest but not need to configure
> >> command line or libivrt xml file then restart guest.
> >>
> >> Using a new QMP command:
> >> -> { "execute": "change-vnc-kbd-layout",
> >> "arguments": { "keymap": "de" } }
> >> <- { "return": {}
> >>
> >> I knew sdl and curses are using keyboard layout, but I don't know
> >> whether they both need to support this feature and add some new
> >> qmp command for them?
> >>
> >> If you have some ideas, please let me know. Thanks!
> >
> > FWIW users of VNC are much better off not setting any keymap at all
> > in QEMU, and then using a client (such as GTK-VNC) that supports the
> > raw scancode extension. This takes QEMU out of the key remapping
> > business entirely, so that everything "just works" with no extra
> > configuration required in QEMU. This is what SPICE does by default
> > too.
>
> 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 ?
Personally I think effort is better spent adding support for the keyboard
extension to more of the various VNC clients that exist. Having to issue
monitor commands to change keymap each time a different client wants to
connect is still a pretty sucky solution IMHO.
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
next prev parent reply other threads:[~2014-12-03 9:56 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 [this message]
2014-12-03 10:04 ` Gonglei
2014-12-03 12:10 ` Gerd Hoffmann
2014-12-04 2:32 ` Gonglei
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=20141203095422.GD10160@redhat.com \
--to=berrange@redhat.com \
--cc=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 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).