From: Theo Honohan <theoh@chiark.greenend.org.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: someone thinking about trying plan 9
Date: Wed, 8 Nov 2000 17:11:59 +0000 [thread overview]
Message-ID: <E13tYlT-0000JG-00@chiark.greenend.org.uk> (raw)
In-Reply-To: Your message of "Wed, 08 Nov 2000 15:09:15 GMT." <tVdO5.81224$YX4.2540049@news2.giganews.com>
In message <tVdO5.81224$YX4.2540049@news2.giganews.com>, cbbrowne@hex.net write
s:
> "david.bates2" <david.bates2@ntlworld.com> writes:
> > I was reading about plan 9 recently. To be frank, I'd never head of it unti
> l
> > a week or two ago... I suppose I was just writing to ask whether it was
> > worth installing at this point in time. I don't doubt that it has some
> > powerful ideas, but does it have any decent apps that run on it at the
> > moment? An example would be apps for spreadsheets, databases, and text
> > editing.... and of course compilers for various langauges. Also, I am a
> > little unclear on the role of rio. Is it the window manager? Is it an
> > essential part of the system or can it be replaced as with a linux window
> > manager?
>
> You're missing a rather _crucial_ point; there is no such thing as a
> "Linux window manager."
That's not a very helpful answer! I wonder whether you might have
missed the word "as" in the second last line...
I think you could say that rio *is* analogous to an X window manager,
in some ways. In the sense that the X window manager is intended to
provide policy and the X server to provide mechanism, rio provides a
particular "window system" implementation on top of the underlying
raster graphics facility (/dev/draw). As such, it provides a set of
window management facilities, while the draw device multiplexes the
display among a number of "clients", to use the X terminology.
You could certainly replace rio with an alternative window system,
although it's probably the case that most of the interesting window
systems you might want to develop in Plan 9 would present a similar
interface. It's conceivable that if you want to have windows that differ
substantially from "asynchronous layers of text" -- some kind of
multimedia, maybe -- then they might be better handled by a different
display management discipline.
Just as you can run a "nested" instance of rio inside a window, you
could run an instance of your new window system within a rio window,
or vice versa. Knock yourself out!
next prev parent reply other threads:[~2000-11-08 17:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-08 9:23 [9fans] " david.bates2
2000-11-08 15:09 ` [9fans] " cbbrowne
2000-11-08 17:11 ` Theo Honohan [this message]
2000-11-08 16:37 anothy
2000-11-08 17:34 anothy
2000-11-09 1:40 okamoto
2000-11-09 7:24 anothy
2000-11-09 11:48 Richard Miller
2000-11-09 17:48 anothy
2000-11-09 17:51 Russ Cox
2000-11-09 18:05 anothy
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=E13tYlT-0000JG-00@chiark.greenend.org.uk \
--to=theoh@chiark.greenend.org.uk \
--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).