9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@labs.coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Good sample GUI code (window creation, management,
Date: Wed, 19 Dec 2012 11:29:24 -0500	[thread overview]
Message-ID: <998b5fd18d839d00a19191682d861a45@coraid.com> (raw)
In-Reply-To: <CABB-WO9svDz5UhCvL2Bqojh6YG7LXosxnjN3gH-NzNRqnnX1EA@mail.gmail.com>

> > I thought I had bumped into a short example on the web for creating
> > a window in C, but can't seem to find it again.
> 
> Plan 9 programs don't create windows, they use the window already
> allocated in their namespace.  This is analogous to programs not
> creating /fd/^(0 1 2) by themselves - they use the ones inherited
> through fork.

that's not quite correct.  by default plan 9 programs use the window
they're in.  but they can create a new window (e.g. page -w).

> account and everything) -- does sam really do its own window
> management -- I mean, it's got overlapping windows and everything so
> that's non-trivial - or does it ask devdraw?  I suppose an easy way to

yes, samterm really does.

> P.S. you might be interested to know that the "theoretical model" of
> how Plan 9's window management works -- that rio serves a fake mouse,
> keyboard, and screen to each of its children -- is wrong.  rio serves

it was correct for 8½.

- erik



  parent reply	other threads:[~2012-12-19 16:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-19 11:14 Luke Evans
2012-12-19 12:59 ` Jacob Todd
2012-12-19 13:02 ` cinap_lenrek
2012-12-19 13:32   ` erik quanstrom
2012-12-19 14:35     ` Giovanni Casano
2012-12-19 14:42       ` erik quanstrom
2012-12-19 14:54         ` Giovanni Casano
2012-12-19 16:07 ` Stuart Morrow
2012-12-19 16:17   ` Dustin Fechner
2012-12-19 16:27     ` Stuart Morrow
2012-12-19 16:29   ` erik quanstrom [this message]
2012-12-20  9:45 ` dexen deVries

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=998b5fd18d839d00a19191682d861a45@coraid.com \
    --to=quanstro@labs.coraid.com \
    --cc=9fans@9fans.net \
    /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).