From: lucio@proxima.alt.za
To: 9fans@cse.psu.edu
Subject: Re: [9fans] PNG and APE (cntd)
Date: Thu, 27 Apr 2006 21:56:39 +0200 [thread overview]
Message-ID: <a6e36e3818769d0d05735a7408f5ac30@proxima.alt.za> (raw)
In-Reply-To: <E1AA4B4A-E01B-48EB-874E-DA7327F747D5@lanl.gov>
> the links web browser also required a port of libpng in a
> subdirectory of its source tree. that's where the test images and
> clients we used against p9's png came from. not sure how useful that
> is, but i thought it worth mentioning.
Yes, I did remember. Like GS, "links" also uses libjpeg, which has
value in itself. GD, libTIFF and GeoTiff all also contribute to a
graphics workbench and all are actually quite open to being converted
to native Plan 9.
That is where I'm hoping to go, but I have some immediate objectives
that have slightly higher priority, as mentioned. In the process,
I've had to make adjustments to the APE headers and to my view of the
Plan 9 directory hierarchy that I hope will benefit others as well.
In the medium term, I think there'd be advantages to extracting zlib,
libpng and libjpeg (at least) from GS, "links" and possibly other
places and accept them as first class citizens in the Plan 9 system.
++L
prev parent reply other threads:[~2006-04-27 19:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-27 4:47 lucio
2006-04-27 6:23 ` Lluís Batlle i Rossell
2006-04-27 17:51 ` lucio
2006-04-27 18:24 ` Lluís Batlle i Rossell
2006-04-27 18:28 ` Charles Forsyth
2006-04-27 19:26 ` Jack Johnson
2006-04-27 19:58 ` Steve Simon
2006-04-27 21:13 ` Lluís Batlle i Rossell
2006-04-27 22:05 ` Charles Forsyth
2006-04-28 5:00 ` lucio
2006-04-28 18:31 ` jmk
2006-04-27 20:02 ` Bruce Ellis
2006-04-27 19:59 ` lucio
2006-04-27 6:36 ` andrey mirtchovski
2006-04-27 6:39 ` andrey mirtchovski
2006-04-27 11:43 ` Lluís Batlle
2006-04-27 11:53 ` Harri Haataja
2006-04-27 12:25 ` Russ Cox
2006-04-27 12:25 ` Russ Cox
2006-04-27 18:18 ` lucio
2006-04-27 18:27 ` andrey mirtchovski
2006-04-27 19:56 ` lucio [this message]
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=a6e36e3818769d0d05735a7408f5ac30@proxima.alt.za \
--to=lucio@proxima.alt.za \
--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).