From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Wed, 28 Jun 2006 19:04:08 -0700 From: Roman Shaposhnick To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Subject: Re: [9fans] [plan9port] graphics Message-ID: <20060629020408.GC17417@submarine> References: Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Topicbox-Message-UUID: 70153ed0-ead1-11e9-9d60-3106f5b1d025 On Wed, Jun 28, 2006 at 10:46:29AM -0700, Russ Cox wrote: > Over the weekend I shuffled things around. Instead of > linking X code into every program, there is now a single > program, called devdraw, that contains X interface code. > Graphical programs now fork and exec a devdraw and then > speak a simple protocol to its standard input and standard > output to read from the keyboard and mouse and draw on the > screen. Devdraw is not a threaded program. It runs on the > standard system stack and uses select(2) to manage its two > inputs. It uses only a single connection to the X server. > My hope is that doing things the Official Unix Way inside > devdraw will eliminate the problems people have reported. This sounds interesting enough, but what's the "language" an application is supposed to talk to devdraw binary in ? Is it just the draw(3) ? Thanks, Roman.