[lug] X11 Protocol, migrating windows to remote displays

D. Stimits stimits at attbi.com
Mon May 19 16:02:07 MDT 2003


Michael J. Hammel wrote:

> On Mon, 2003-05-19 at 00:43, Nate Duehr wrote:
>
> >I've only read about it, but isn't this kinda what x2x does?  Maybe 
> not...
> >you want the ability for another machine to "steal" stuff off the
> >windowmanager of another... but x2x supposedly allows you to display one
> >desktop across multiple X servers, right?
>
>
> Going by the project details @ freshmeat, I'd say no.  It just allows
> local user input devices to control a multiple (and remote) X servers.
> Unless theres more to it, it doesn't appear to allow moving the clients
> to the remote display.

This is correct. I contemplate extending x2x to include joystick events 
as well, although there are some complications. For example, each 
machine already has a mouse and keyboard, and moving a mouse from one 
machine to another acts like an "overlay", in that both mice work at the 
same time, and the X11 server does not care which mouse is moving (ditto 
for keyboard). Now if one mouse type on one machine is different than 
the one for the other machine, and if the mice are at least compatible, 
then get the minimum subset of overlapping features that both mice 
support, e.g., scroll wheel will not work from the first machine if the 
second machine has a mouse type that does not support wheel. In order to 
extend it to support joystick, both machines would have to have the same 
time of joystick for it to be useful (it isn't an input device 
replacement, it is an input device shadow utility).

Now if I want to do development where my IDE has set $DISPLAY to a 
remote machine, I can do this, but that means 100% of the displayed app 
will be on one machine or the other...it isn't possible to use both 
monitors to see more desktop space with different editors on each monitor.

D. Stimits, stimits AT attbi DOT com




More information about the LUG mailing list