From: Daniel Skarda <0rfelyus@atrey.karlin.mff.cuni.cz>
To: guile-gtk@sourceware.cygnus.com
Subject: Re: Pixmaps
Date: Wed, 15 Dec 1999 04:03:00 -0000 [thread overview]
Message-ID: <m0yaawmmws.fsf@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <38566ADC.867254D3@niss.org>
> The most serious gap in guile-gtk found so far when translating the
> tutorials (14/42 done) is the lack of support for coded-in xpms.
Similar gap is in guileGL - there is still no way how to specify textures. IMHO
in Guile there should be one standard way how to access images. To specify
texture in OpenGL means just to pass pointer to some area in memory - so this
can be realized in guileGL bindings by (uniform) arrays. But in my opinion it
is ugly to specify pictures in guile-gtk in one way and in bindings for another
library in completely different way....
Any proposals for "(define-module (graphics images))" ???
Dan Skarda
next prev parent reply other threads:[~1999-12-15 4:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-14 8:05 Pixmaps Alex Stark
1999-12-15 4:03 ` Daniel Skarda [this message]
1999-12-15 6:22 ` Pixmaps Alex Stark
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=m0yaawmmws.fsf@atrey.karlin.mff.cuni.cz \
--to=0rfelyus@atrey.karlin.mff.cuni.cz \
--cc=guile-gtk@sourceware.cygnus.com \
/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).