michalsrb

Plan

VNC protocol transfers key symbols (= basically characters), not key codes (= "coordinates" on keyboard). Therefore pressing the same keys may result in sending different commands over VNC depending on the keyboard layout and state of modifiers on the client side. The server however can not directly send the key symbol to the application, it must instead find or create key code that will translate to that symbol and send that.

The goal is to jump forward with this fate: https://fate.suse.com/319319

Tigervnc comes with two very similar VNC viewers - one written in C++ and one in java. The java one can be embedded in a webpage as a java applet. We use that in our default VNC setup (the one enabled in YaST). That way if user doesn't have VNC viewer installed, browser is enough.

This is preparation/accompanying project to my school thesis.

I use the KDevelop IDE whenever I can. At SUSE mostly for reading code while debugging some bug. My plan is to create plugin that will show extra information inline with the code to make it easier to explore foreign code.