[Date Prev] [Date Next] [Thread Prev] [Thread Next] Date Index Thread Index Search archive:
Date:Mon Aug 3 20:39:19 1993 
Subject:Re: Prodding Ved from the Outside 
From:Steve Knight 
Volume-ID:930804.01 

jonm (Jonathan Meyer) (jonm@uk.co.integ) wrote:

> I have thought quite a bit about this topic recently - it would be useful
> in general to be able to send messages to a Poplog running on a display.
>
> My solution would be to use X Windows `properties' to communicate messages
> to Poplog processes running on a display.

This sounds like an excellent idea to me.  I'd like to see it added
to POPLOG in such a way that a single procedure call would initialise
everything.


> I would create a property on the root window of the user's display,
> say called __POPLOG_MESSAGE_WINDOWS. This would be a list of window IDS
> representing the Poplog processes running on that display.

Adding and deleting elements from this list would presumably require
some kind of "locking" to prevent nasty accidents.  Can this be done
through grabbing the server?


> You could very easily imagine a system where Poplog processes can create
> multiple message windows, each with different names. The message sending 
> program would be altered to not only search for valid window ids, but also 
> look for windows with a specific name. Then you could have multiple message 
> contexts. You might then do:

This extension seems almost mandatory to cope with the situation of
many Poplog's running simultaneously.  Furthermore, it is probably
necessary to be able to create several windows (to be able to handle
messages concerned with several different topics).  I would also guess
that Poplog would need a way -- just like the C program -- what 
message-windows were available.

Steve