From: erik quanstrom <quanstro@quanstro.net>
To: quanstro@quanstro.net, Russ Cox <rsc@swtch.com>
Cc: 9fans@cse.psu.edu
Subject: Re: [9fans] Plan9Ports libdraw open-in-same-window
Date: Fri, 10 Mar 2006 08:53:27 -0600 [thread overview]
Message-ID: <20060310145327.28F31159EF6@dexter-peak.quanstro.net> (raw)
In-Reply-To: <f31092348eeaf2102347ec79892c0919@swtch.com>
i agree that requiring libthread would be a downside.
however, there are few p9p programs which libdraw and are still
single threaded. i did a little search and came up with these:
scat, proof, plot, page, htmlfmt, jpg/*
they might not even need modification to work.
to make X happy, you'd want a 1:1 correspondence
between devdraw servers and windows. then if the
devdraw-like server crashes, only one window would go
down.
i think the bottom line is that X is a pain in the rear.
- erik
"Russ Cox" <rsc@swtch.com> writes
|
| > the upside of all this is that window and rio would be the only programs
| > linked against X. the downside would be extra 9p traffic.
|
| and requiring libthread (for lib9pclient) to write a gui program.
| i'm not thrilled about that. also, i did something similar before
| with the windows port attempt, and it was very annoying when
| the devdraw-like server would crash and take everything with it.
|
| russ
next prev parent reply other threads:[~2006-03-10 14:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-09 21:36 Paul Lalonde
2006-03-09 21:40 ` Russ Cox
2006-03-09 22:21 ` Paul Lalonde
2006-03-10 0:38 ` Russ Cox
2006-03-10 1:00 ` Paul Lalonde
2006-03-10 1:14 ` Russ Cox
2006-03-10 3:15 ` Paul Lalonde
2006-03-10 3:34 ` Russ Cox
2006-03-10 4:26 ` Paul Lalonde
2006-03-10 3:35 ` Russ Cox
2006-03-10 6:50 ` Bruce Ellis
2006-03-10 14:25 ` Russ Cox
2006-03-10 13:55 ` erik quanstrom
2006-03-10 14:29 ` Russ Cox
2006-03-10 14:53 ` erik quanstrom [this message]
2006-03-10 15:03 ` Russ Cox
2006-03-10 15:21 ` erik quanstrom
2006-03-10 15:26 ` Russ Cox
2006-03-10 17:08 ` erik quanstrom
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=20060310145327.28F31159EF6@dexter-peak.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@cse.psu.edu \
--cc=rsc@swtch.com \
/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).