From: "Doug Henderson" <djhender@telusplanet.net>
To: <9fans@cse.psu.edu>
Subject: [9fans] ugrading edition 2 graphics to edition 3
Date: Wed, 2 Aug 2000 07:23:20 -0600 [thread overview]
Message-ID: <007001bffc84$d5efac00$0500a8c0@telusplanet.net> (raw)
While I looked at Plan9 a number of years back - I downloaded the 3 disk
install set I think, I didn't get seriously involved until 3rd edition, what
with ADSL & cable making 50Meg downloads a practicality for the individual.
A lot of the existing native plan9 source code out there is written for the
2nd edition graphics libraries, with headers like <libg.h>, <panel.h>, and
<layer.h>. I don't have access to the 2nd edition graphics library
documention. I have not seen both versions of any programs which have been
transformed from 2nd to 3rd editions.
One of the most valuable aids (for me) to learning a new environment is
building and experimenting with existing code. So I am lacking some of the
tools that I can use to figure out how to do these tranforms. Is the 2nd
edition documentation still available anywhere, for download or browsing? Is
there a porting guide? A feature comparision?
The <libg.h> looks like it used to be supported in the APE environment (the
header is still there in 3rd, but it doesn't work - also no libg.a). Is the
3rd edition <draw.h> and etc. going to be supported under the 3rd edition?
Anyone working on that? Are there guidelines / suggestions for doing such a
thing? My efforts so far get to the linker where I get a conflict between
the ape atexit and the libc atexit (I think).
Are there any feature test programs available? I mean simple programs
(perhaps used by the developers of the 3rd edition graphics libraries) to
excercise the features of the code. I find these kinds of programs a
valuable starting point for testing out my own pieces of code - the ones
where I find out how to do the basic things I need for a larger project.
next reply other threads:[~2000-08-02 13:23 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-02 13:23 Doug Henderson [this message]
2000-08-02 14:45 rob pike
2000-08-03 8:20 ` Boyd Roberts
2000-08-03 8:44 ` Doug Henderson
2000-08-03 8:54 ` Boyd Roberts
[not found] ` <boyd@noos.fr>
2000-09-11 15:41 ` Tom Duff
2000-08-02 16:53 Anthony Sorace
2000-08-02 20:33 Russ Cox
2000-08-03 19:13 dhog
2000-08-03 20:19 geoff
2000-08-04 16:19 ` Douglas A. Gwyn
2000-08-04 17:06 ` Matt
2000-08-07 8:44 ` Douglas A. Gwyn
2000-08-03 20:40 forsyth
2000-08-03 23:43 kim kubik
2000-08-04 9:12 ` Boyd Roberts
2000-08-04 14:19 ` Andy Newman
2000-08-04 14:37 ` Boyd Roberts
[not found] ` <20000805004518.A42947@juju.bsn>
[not found] ` <022101bffe66$90ac6640$03c684c3@psychobasketcase.org>
[not found] ` <20000805085453.A46136@juju.bsn>
2000-08-04 23:26 ` Boyd Roberts
2000-08-07 8:46 ` Alex Danilo
2000-08-07 13:41 ` Andy Newman
2000-08-07 20:45 ` Boyd Roberts
2000-08-04 8:25 forsyth
2000-08-04 17:02 nigel
2000-08-07 8:44 ` Douglas A. Gwyn
2000-08-05 2:18 geoff
2000-08-05 2:27 Anthony Sorace
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='007001bffc84$d5efac00$0500a8c0@telusplanet.net' \
--to=djhender@telusplanet.net \
--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).