rlk@THINK.COM (Robert L Krawitz) (06/27/90)
Date: 26 Jun 90 16:00:56 GMT From: cunixf.cc.columbia.edu!reha@rutgers.edu (Reha Elci) Since X already has the client/server approach, one client program can already open any display. What is missing is multiple displays + event mirroring. I guess there would be an artificial way of doing this if I replace XtAppMainLoop to send the same events to multiple displays. This would be quite useful in training sessions where proximity to other sites preclude possibility of demonstration using single client & server. It also makes support much easier when, say, a remote user is trying to demonstrate a bug in result of a sequence of events. Along similar lines, broader support for multi-display and transferring of applications between displays, along with error recovery (XReopenDisplay?). Saber C already does this, and it's very handy. While this is admittedly likely to be application specific, having hooks at the Xt level (for example) would strongly encourage people to take advantage of this facility. Somewhat to my surprise (the thing was a real hack), the old X10 x-change-display function in GNU Emacs is something that several people around here seem to want. That function never really addressed the resource (in those days, the X default) issue, but perhaps it would be possible to work out where such a client would get its resources from. ames >>>>>>>>> | Robert Krawitz <rlk@think.com> 245 First St. bloom-beacon > |think!rlk (assistant postmaster) Cambridge, MA 02142 harvard >>>>>> . Thinking Machines Corp. (617)876-1111