From: gregarican <greg.kujawa@...>
Date: 2005-06-11T03:10:29+09:00
Subject: Re: framework of Ruby/Tk + VNC

Hidetoshi NAGAI wrote:

> In this case, I use the following way.
>
> * Xvnc is started from inetd and connected to X Display Manager
>   (Xvnc -inet -query localhost ...).
>
>
> * X Display Manager starts up a greeter on the X (Xvnc) server.
>   But the greeter is replaced to a Ruby/Tk application launcher.
>
>
> * The application launcher do setup steps (if needed),
>   and executes Ruby/Tk.
>   So, the Ruby/Tk process is placed on a window manager proces.
>
>
> * When the Ruby/Tk process is finished,
>   Xvnc treats it as the end of Xsession, and shuts down the socket.
>
>
>--
>

Oh I see now. In the past I have used VNC on everything from Sharp
Zaurus PDA's to Linux boxes to my Windows boxes. But I hadn't looked
"under the hood" to see how it connected for sessions. In terms of the
Ruby/Tk framwork for it I was thinking in terms of my Windows
environment. And I wasn't sure of a way to redirect a VNC session from
the default window manager (i.e. - Windows itself). But this makes
sense how you can redirect things through the Xvnc/XDM session for the
non-Windows world. There's a lot more flexibility there.

Great work. I must say I am constantly impressed with the Ruby
community. It is friendly, knowledgeable, and has a very mature
application/binding collection. This is just another example.