From: william@thinktankworkspaces.com
To: 9front@9front.org
Subject: Re: [9front] [patchset] libgeometry revamp
Date: Sun, 29 Jan 2023 17:25:37 -0800 [thread overview]
Message-ID: <760DDEAEAA34C2CCD2EB2195D73D0AED@thinktankworkspaces.com> (raw)
In-Reply-To: <A9C4BF8081E5989A24A3C8CE20915A91@antares-labs.eu>
Brilliant!
Quoth rgl@antares-labs.eu:
> hello everyone,
>
> this is a proposal to renovate the current libgeometry with a more
> modern implementation that i've been using in my personal projects for
> the last four years. it provides almost all of the functionality
> available in the old one, with a cleaner and more consistent interface
> (similar naming conventions as those used in libdraw's geometric
> routines), plus the addition of 2D transformations (not just 3D), a
> frame of reference data type for 2- and 3-spaces, and utilities such
> as point-in-polygon testing and barycentric coordinate computations.
>
> i documented everything in a single man page—geometry(2)—, so i got
> rid of those related to the old library, with the exception of
> qball(2), on which i'm still working and whose implementation i
> believe to be broken; i'm using a version by BurnZeZ with some minor
> changes that actually works, but it doesn't perform rotations the way
> it should (demo: https://www.youtube.com/watch?v=g3pha1EXhIk) and i
> will need more time to come up with a proper Arcball controller.
>
> some examples of projects where i use the library:
>
> - http://git.antares-labs.eu/boids/
> - http://git.antares-labs.eu/etoys/
> - http://git.antares-labs.eu/gamephysics/
> - http://git.antares-labs.eu/3dee/
>
>
> if it looks reasonable to you, i can push it upstream.
>
>
>
> cheers!
>
> -rodri
>
prev parent reply other threads:[~2023-01-30 1:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-29 18:47 rgl
2023-01-29 20:49 ` cinap_lenrek
2023-01-29 22:46 ` rgl
2023-01-30 11:17 ` Anthony Martin
2023-01-30 16:49 ` rgl
2023-01-29 22:48 ` sirjofri
2023-01-30 1:25 ` william [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=760DDEAEAA34C2CCD2EB2195D73D0AED@thinktankworkspaces.com \
--to=william@thinktankworkspaces.com \
--cc=9front@9front.org \
/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).