From: Daniel Hartwig <mandyke@gmail.com>
To: Javier Sancho <jsf@jsancho.org>, guile-user <guile-user@gnu.org>
Subject: Re: Guile OpenGL bindings
Date: Fri, 1 Feb 2013 21:29:36 +0800 [thread overview]
Message-ID: <CAN3veRdVj_Yzh4gGfqP4_QY4tU_cRG=nbV+_rdxuDP1K9zW-3w@mail.gmail.com> (raw)
In-Reply-To: <CAPH5TQHJgK7RLVwfLH0rrnZoQTx9DkToYEcj5krjJ=q3m51B9g@mail.gmail.com>
On 1 February 2013 21:02, Javier Sancho <jsf@jsancho.org> wrote:
> Aleix Conchillo is also working with OpenGL and encountered a problem
> with glutInit and char**. You can see it at
> http://lists.gnu.org/archive/html/guile-devel/2012-07/msg00074.html
Mark's suggestion is spot on, even points out one issue with memory
that I have missed.
It seems that Aleix later moved to a C binding, though I am confident
this can be avoided (c.f. cl-opengl). Anyway, this function is
working fine in the bindings I have prepared (sans the memory issue).
GLUT bindings cover all functions, but missing constants. These to
follow shortly.
Andy's work on the sxml side has the GL bindings *almost* running as
well. I'll look to finish those in the next few days if someone
doesn't beat me to it.
> Someone mentioned performance issues when using FFI, too.
For modern GL programming without glBegin/End, Vertex/Color/Normal,
etc. the performance impact of FFI should be negligable. There are
few GL calls compared to the volume of data that is passed.
The real critical part will be how the user manipulates their vertex
data, if this is done frequently on the scheme side. Mapping (typed)
bytevectors, or srfi-4 to gl arrays will help with that, and avoiding
the implicit type conversions that some other bindings perform.
> Well, I can't promise anything, but yes, I'm very interested in this project.
Nice.
next prev parent reply other threads:[~2013-02-01 13:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-01 12:16 Guile OpenGL bindings Andy Wingo
2013-02-01 13:02 ` Javier Sancho
2013-02-01 13:29 ` Daniel Hartwig [this message]
2013-02-01 15:10 ` Mark H Weaver
2013-02-01 20:56 ` vimml
2013-02-01 23:54 ` Daniel Hartwig
2013-02-02 7:10 ` Aleix Conchillo Flaqué
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAN3veRdVj_Yzh4gGfqP4_QY4tU_cRG=nbV+_rdxuDP1K9zW-3w@mail.gmail.com' \
--to=mandyke@gmail.com \
--cc=guile-user@gnu.org \
--cc=jsf@jsancho.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 read-only IMAP folder(s) and NNTP newsgroup(s).