From: "Russ Cox" <rsc@swtch.com>
To: 9fans <9fans@cse.psu.edu>
Subject: [9fans] request: native graphics on OS X
Date: Sun, 10 Dec 2006 17:33:53 -0500 [thread overview]
Message-ID: <ee9e417a0612101433o13acee41l2d486c721a6dcbea@mail.gmail.com> (raw)
If there is someone out there who has a Mac and some spare cycles,
please Please PLEASE look into writing a Carbon-based (not X11-based)
back end for drawterm or for Plan 9 ports (if you do one, I'll do the other!).
The only hard part is finding out how to interface with Carbon from C.
The demands that Plan 9 graphics make on the underlying system
are really very minimal, the X implementation notwithstanding.
As a simple example take a look at the win32 code in drawterm,
which is only 646 lines to deal with mouse, keyboard, and graphics window.
http://cvs.pdos.csail.mit.edu/cvs/drawterm/gui-win32/screen.c?annotate=1.4
Ron's mention of a /dev/fb-based draw setup is similar proof.
If you know of good documentation but don't have time, please post any
links to docs that might help someone else.
Thanks.
Russ
next reply other threads:[~2006-12-10 22:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-10 22:33 Russ Cox [this message]
2006-12-10 23:01 ` [9fans] " Russ Cox
2006-12-10 23:23 ` Paul Lalonde
2006-12-10 23:41 ` Russ Cox
2006-12-11 0:05 ` Paul Lalonde
2006-12-11 1:38 ` Paul Lalonde
2007-01-09 21:39 ` David Leimbach
2007-01-09 22:22 ` Russ Cox
2007-01-09 22:42 ` Paul Lalonde
2007-01-10 0:05 ` Brantley Coile
2007-01-10 0:58 ` andrey mirtchovski
2007-01-10 1:01 ` Brantley Coile
2007-01-10 1:05 ` andrey mirtchovski
2007-01-10 1:07 ` Brantley Coile
2007-01-10 1:24 ` andrey mirtchovski
2007-01-10 5:09 ` David Leimbach
2007-01-10 5:18 ` andrey mirtchovski
2007-01-10 1:05 ` Paul Lalonde
2007-01-10 16:39 ` Abhey Shah
2007-01-10 16:46 ` David Leimbach
2007-01-10 9:20 ` Skip Tavakkolian
2007-01-10 16:07 ` David Leimbach
2007-01-10 16:39 ` Paul Lalonde
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=ee9e417a0612101433o13acee41l2d486c721a6dcbea@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).