9front - general discussion about 9front
 help / color / mirror / Atom feed
From: "Rodrigo G. López" <rgl@antares-labs.eu>
To: 9front@9front.org, qwx@sciops.net
Subject: Re: [9front] qball(2) bounced back
Date: Sat, 18 May 2024 18:43:15 +0000	[thread overview]
Message-ID: <CF9E8E0C-98D0-49AC-BE0A-8CBA4C11E2AD@antares-labs.eu> (raw)
In-Reply-To: <DFB9D0415B4B80DDE148ABF9B2637733@wopr.sciops.net>

i guess it's a matter of keeping it simple, i mean, ideally i would not put it in any of those places, but take the input devices/controls out of libdraw and into their own libui (or whatever we could call it) and add it there.

the qball is very much a graphics thing, and libgeometry's job is to focus on geometry, not visualization—related as they are. graphics libraries should depend on it, not the other way around.

…but maybe i'm being too pedantic.

i will add all of this eventually, as long as it's welcome (it's a lot of code), so i was thinking i put it in libgraphics, then merge it when the time comes. :)


-rodri

On May 18, 2024 3:49:02 PM UTC, qwx@sciops.net wrote:
>On Sat May 18 12:06:14 +0200 2024, rgl@antares-labs.eu wrote:
>> hello everyone,
>> 
>> i recently fixed the qball, after almost a year and a half of me saying i would:
>> 
>> 	http://git.antares-labs.eu/3dee/plain/qball.c
>> 
>> it is consistent with the conventions used in libgeometry, and it works by
>> default when looking at a model from the positive z-axis (just like Shoemake's).
>> 
>> the thing is, i've been thinking about it, and it doesn't make sense to
>> put it in there. it is actually a perfect fit for mouse.h with its menuhit(2)
>> and enter(2) routines; the problem is that this would make libdraw depend on
>> libgeometry, or require to keep a copy of the Quaternion procedures used for
>> the qball—and make sure they are in sync with libgeometry.
>
>Awesome, 3dee is really cool :) Performance isn't great but it works
>nicely.
>
>Why not leave qball in libgeometry?  Isn't it implicit that you'd be
>using both libgeometry and mouse+keyboard with qball anyway?  If so,
>imho it's fine.  libdraw et al aren't as cleanly delineated as they
>could be, so these sorts of dependencies are common.
>
>I'd personally be happy to see all of this part of the distro, it's
>very interesting and throrougly in plan9 style, but it's just my
>opinion (minus some of the model files of course).
>
>Cheers,
>qwx

      reply	other threads:[~2024-05-18 18:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-18 10:00 rgl
2024-05-18 15:49 ` qwx
2024-05-18 18:43   ` Rodrigo G. López [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=CF9E8E0C-98D0-49AC-BE0A-8CBA4C11E2AD@antares-labs.eu \
    --to=rgl@antares-labs.eu \
    --cc=9front@9front.org \
    --cc=qwx@sciops.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).