From: LM <lmemsm@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] user interface questions
Date: Mon, 29 Apr 2019 14:56:05 -0400 [thread overview]
Message-ID: <CAFipMOHpS_CYbf9vPwLuZnNUY7SDST7jcuQw5CCeGtJhZUYOUw@mail.gmail.com> (raw)
In-Reply-To: <mailman.1.1556366401.10382.9fans@9fans.net>
On Sat, Apr 27, 2019 at 8:01 AM <9fans-request@9fans.net> wrote:
> There is some snapshots of the broken link
> (http://fabrice.bellard.free.fr/TinyGL/) in archive.org, but the link
> to the source is missing. For example:
> https://web.archive.org/web/20080506105341/http://fabrice.bellard.free.fr/TinyGL
Thanks. I do already have the original source code for TinyGL, plus
source code to over a dozen forks. I'm working on incorporating the
best of the various forks into one fork. Was there anything already
done or that still needs to be done to get this working specifically
with Plan 9? I believe I saw some mention of SDL ported to Plan 9 (
https://9p.io/wiki/plan9/contrib_index_test/index.html ). If that's
working, then the forks of TinyGL that use SDL as a backend should
work fine with it as is. Some forks also allow for alternative
backends like vesa framebuffer or nano-x/microwindows (which works on
a variety of operating systems from DOS and embedded systems to mobile
devices to Linux and Windows).
Sincerely,
Laura
next parent reply other threads:[~2019-04-29 18:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1556366401.10382.9fans@9fans.net>
2019-04-29 18:56 ` LM [this message]
2019-04-26 20:37 Antonio Barrones
2019-04-26 20:41 ` Kurt H Maier
2019-04-27 6:10 ` Lucio De Re
2019-04-27 7:28 ` Jens Staal
2019-05-05 8:44 ` Lucio De Re
-- strict thread matches above, loose matches on Subject: below --
2019-04-25 18:50 LM
2019-04-29 11:20 ` Ethan Gardener
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=CAFipMOHpS_CYbf9vPwLuZnNUY7SDST7jcuQw5CCeGtJhZUYOUw@mail.gmail.com \
--to=lmemsm@gmail.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).