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 > >
