All of lore.kernel.org
 help / color / mirror / Atom feed
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 17:46:22 +0800	[thread overview]
Message-ID: <54802D6E.4080704@huawei.com> (raw)
In-Reply-To: <1417682821.14168.128.camel@nilsson.home.kraxel.org>

On 2014/12/4 16:47, Gerd Hoffmann wrote:

>   Hi,
> 
>> 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!
> 
> The alternatives are:
> 
>  * Try figure why they are using tightvnc.  Do they simply don't know
>    there are other vnc clients such as remote-viewer with much better
>    keyboard support?  Did they try other clients and want stick to
>    tightvnc nevertheless?  If so, what are the reasons?
> 

As far as I can tell, they integrate tightvnc into a web page (tightvnc
realized by Java) as a jar file in Desktop Cloud scenario on windows guests.
I don't know virt-viewing/remote-viewer whether work well on windows
platform?

Regards,
-Gonglei

>  * Try add raw scancode extension support to tightvnc (or the
>    http://tigervnc.org/ fork).
> 
> I see server-side keymap switching as last ressort if all other
> approaches failed, simply because the manual keymap configuration needed
> on the server side is error-prone and a pretty bad user experience.
> 
> cheers,
>   Gerd
> 
> 

  reply	other threads:[~2014-12-04  9:50 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
2014-12-04  8:47         ` Gerd Hoffmann
2014-12-04  9:46           ` Gonglei [this message]
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=54802D6E.4080704@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.