9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@swtch.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] [plan9port] graphics
Date: Thu, 29 Jun 2006 08:36:41 -0700	[thread overview]
Message-ID: <ee9e417a0606290836y69185635q464995f44229a61e@mail.gmail.com> (raw)
In-Reply-To: <ea8273d90ebb08083f50ce5ccfca3afc@quanstro.net>

> when this came up a while ago, you suggested one devdraw
> server per namespace.  after some consideration i convinced
> myself you were right.  programs like rio could be much closer
> to the plan 9 source.  lately i've been considering writing an
> X server extension implementing devdraw.  (i realize this might
> be problematic on osx.)
>
> why did you choose to run 1 devdraw per graphical program?

i still think that the right long-term solution is
a single devdraw that can handle many windows.
this was easier to get running and get right
(which is not to say that it worked the first time!),
and i don't want to waste any more time on x
than i already have.

responding to earlier questions, you're still supposed
to use draw(3).  drawfcall(3) is subject to change.

russ


  reply	other threads:[~2006-06-29 15:36 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
2006-06-29  4:27 ` quanstro
2006-06-29 15:36   ` Russ Cox [this message]
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=ee9e417a0606290836y69185635q464995f44229a61e@mail.gmail.com \
    --to=rsc@swtch.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).