[vbox-dev] vrde with vnc
geoffn at gnaa.net
Sat May 5 22:28:06 PDT 2012
On 12-03-07 01:33 PM, Christophe Devriese wrote:
> Thanks !
> This was based on the contributions of the FreeBSD team, so a big
> thanks to them too. And of course the libvncserver made all this
> possible in the first place.
> On Wed, Mar 7, 2012 at 2:28 PM, Klaus Espenlaub
> <klaus.espenlaub at oracle.com <mailto:klaus.espenlaub at oracle.com>> wrote:
> On 08.11.2011 22:22, Christophe Devriese wrote:
> I tried getting this integrated. It's not working. But here's
> you can build as an extpack, and it contains docs. If anybody
> knows how to move forward with this (maybe have an "unofficial
> ftp location or something, where oracle doesn't claim ownership or
> quality or anything ???)
> It's in the VBox tree now... finally found some time. A few words
> of documentation are in the manual, too.
> I hope that the deb/rpm package build logic is now also working,
> this was quite a bit of work to figure out how it should be done
> properly. For those builds the VNC "extpack" is included in the
> normal package, as anything else makes little sense.
> Additionally, it would be *great* to have a way to get custom QT
> interfaces and configuration file formats into extpacks. There
> was some
> work on this but, and it was implemented for the UDPTunnel
> stuff, but ...
> This shouldn't need custom hacking - the listen address/port
> works, and the VNCPassword stuff shouldn't be too hard either, if
> we get to adding generic VRDE property editing support in the GUI.
> Of course a few changes are necessary, to get over the "RDP"
> centric labels ;)
> Anyway, here's the file. It shows how to build and register
> the extpack,
> and how to get the extpack to operate (I'm afraid you will be
> python commands to enable this for a specific VM instance).
> Also, I'm having trouble finding the time to work on this, and
> I don't
> really have a place to put this online. If anybody's willing to do
> something like this ? I'd rather not put it on github or
> something like
> that, as it'll just get fragmented and we'll end up with 10
> versions, all with weird bugs.
> I always planned to give it a home in the VBox source tree. No
> promises if we'll make binaries available or if we leave this to
> others. The most likely variant is the latter.
> Anyway, let me know what you think. Good luck with it.
> The contribution was a great starting point. Needed some cleanup,
> and I couldn't resist implementing some optional features, just to
> illustrate what's possible.
> Oh, and I had a go at the keyboard handling (Caps/Scroll/Num Lock
> not handled, AltGr not handled, and keypad support was a commented
> out theory). It's of course still unusable (or at least bad) on
> non-US keyboards, because in general reverse mapping from X
> keysyms to scancodes is impossible. For simple keyboard layouts
> it's doable, but even there knowledge of the keyboard map is
> required, and this isn't there at all.
> Thank you very much for the effort you all put into this, and if
> you (or anyone else) has improvements, just let us know. Now that
> the base code is in the tree it's a lot easier to integrate
> On Mon, Nov 7, 2011 at 8:41 AM, Klaus Espenlaub
> <klaus.espenlaub at oracle.com
> <mailto:klaus.espenlaub at oracle.com>
> <mailto:klaus.espenlaub at oracle.com
> <mailto:klaus.espenlaub at oracle.com>>> wrote:
> On 05.11.2011 00:45, Geoff Nordli wrote:
> On Friday, November 04, 2011 06:24:17 PM Perry Halbert
> I guess I am confused. You can compile VBox with
> the VNC
> (VBOX_WITH_VNC :=1) already.
> Not sure about Windows though. Is that what this
> is about?
> On 11/04/2011 05:41 PM, Geoff Nordli wrote:
> Howard Su was talking about VNC and VRDE back
> in February.
> Has there been any more work done with this?
> This hasn't been fully integrated yet. I agree that this would
> improve the VNC user experience significantly.
> Hi Perry.
> Being able to control it via the API is the main thing I am
> looking for.
> There is a chance of having this in 4.1, if an engineer
> finds enough
> time and the change including the cleanup is low risk. In
> any case,
> it will first go into trunk.
I am trying to get a better understanding of how this all works together
in preparation for the 4.2 release (whenever that happens).
This work is based on the libvncserver project. Does this mean that we
can use the latest version (0.9.9) with support for noVNC HTML5 VNC
Viewer (http://kanaka.github.com/noVNC/) and websockets. I have a
feeling that we are going to need to manually compile the extension
(which is fine).
I am a little bit confused about the keymap discussion. Doesn't the VNC
client connect directly to the vncserver?
It seems that password part is stored using the vboxmanage command.
Could this be set via the Webservice API?
Will VNC be able to be managed by the VRDE API?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the vbox-dev