Multi-process curses?

[David Goodenough]

>From article <687 at vsi.UUCP>, by friedl at vsi.UUCP (Stephen J. Friedl):
>      Generally speaking, we want curses to know about the other
> sessions.  If we put curscr in shared memory (again, speaking
> generally), and can "somehow" link the various windows structures
> together, with a little mutex around the shared access, it seems
> that this could be extended generally to a pretty slick little
> windowing system where child curses processes would be largely
> unaware that they were running in a multi-process environment.
> Has anybody done this?  Are we out of our minds?

Basically, as I read it, you want several processes to be able to output to
curses and have everything look sensible. Why not create a "curses server"
which uses a socket / named pipe mechanism to receive curses requests, and
then does them. That way you only have one "curses environment", but it
fields all the requests. As to the exact nature of a request I'll leave that
for you to decide (I am not going to do system design for a software package
based on a single screen description :-) :-), but with a scheme such as
this it should be possible.

	Comments (Flames :-) anyone?
-- 
	dg at lakart.UUCP - David Goodenough		+---+
							| +-+-+
	....... !harvard!adelie!cfisun!lakart!dg	+-+-+ |
						  	  +---+