9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "David Leimbach" <leimy2k@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] [plan9port] graphics
Date: Wed, 28 Jun 2006 20:59:38 -0700	[thread overview]
Message-ID: <3e1162e60606282059q845f4aare490422cf7f37b81@mail.gmail.com> (raw)
In-Reply-To: <20060629020408.GC17417@submarine>

On 6/28/06, Roman Shaposhnick <rvs@sun.com> wrote:
> 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.
>

I'd think you're still supposed to talk in draw(3) for portability's
sake right? :-)

Some protocols don't have to be fully open, but it might be
interesting to know about them.

Dave


  reply	other threads:[~2006-06-29  3:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-28 17:46 Russ Cox
2006-06-28 21:13 ` Jack Johnson
2006-06-28 21:42   ` Russ Cox
2006-06-29  2:04 ` Roman Shaposhnick
2006-06-29  3:59   ` David Leimbach [this message]
2006-06-29  4:27 ` quanstro
2006-06-29 15:36   ` Russ Cox
2006-06-29 18:59     ` Roman Shaposhnick
2006-07-12 15:36       ` andrey mirtchovski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3e1162e60606282059q845f4aare490422cf7f37b81@mail.gmail.com \
    --to=leimy2k@gmail.com \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).