From: "Bill Schottstaedt" <bil@ccrma.Stanford.EDU>
To: JonWilson <jsw@wilsonjc.us>
Cc: guile-user@gnu.org
Subject: Re: What new libraries or functionality does Guile need?
Date: Tue, 22 Jul 2008 06:09:47 -0700 [thread overview]
Message-ID: <20080722130522.M76192@ccrma.Stanford.EDU> (raw)
In-Reply-To: <4884B316.4020105@wilsonjc.us>
> Would it be possible for the snd team to spend
> some time factoring out these things?
There's a short answer, and a very long answer that would take me
several hours to compose. The short one is that two large sections
have been extracted into stand-alone libraries: sndlib and xmlib.
sndlib includes the sound file accessors, audio device handlers,
a package of array processing stuff, and a package of sound
synthesis functions. xmlib includes bindings for Motif, Xt, X,
Glib, Gdk, Gtk, cairo, and openGL. These are available at
ccrma's ftp site:
ftp://ccrma-ftp.stanford.edu/pub/Lisp/sndlib.tar.gz
ftp://ccrma-ftp.stanford.edu/pub/Lisp/libxm.tar.gz
xen.h has macros to deal with all the changes from Guile 1.3.4
to the present. I could extract more from Snd, the axis drawing stuff
for example, or the optimizer, but most of the code is specific to editing and
synthesizing sounds.
next prev parent reply other threads:[~2008-07-22 13:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cmu-lmtpd-23333-1216458306-3@mail-imap1.uio.no>
2008-07-19 11:08 ` What new libraries or functionality does Guile need? Kjetil S. Matheussen
2008-07-21 16:02 ` JonWilson
2008-07-22 13:09 ` Bill Schottstaedt [this message]
[not found] <cmu-lmtpd-5742-1216742728-1@mail-imap1.uio.no>
2008-07-22 16:24 ` Kjetil S. Matheussen
2008-07-18 19:43 dsmich
-- strict thread matches above, loose matches on Subject: below --
2008-07-18 19:37 dsmich
2008-07-18 18:38 Mike Gran
2008-07-18 17:13 Mike Gran
2008-07-18 17:39 ` Julian Graham
2008-07-18 18:32 ` Andre Kuehne
2008-07-19 0:40 ` Jose A. Ortega Ruiz
2008-07-19 5:49 ` Maciek Godek
2008-07-19 18:10 ` Bill Schottstaedt
2008-07-20 20:42 ` Ludovic Courtès
2008-07-20 22:35 ` Mike Gran
2008-07-21 6:34 ` Thien-Thi Nguyen
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=20080722130522.M76192@ccrma.Stanford.EDU \
--to=bil@ccrma.stanford.edu \
--cc=guile-user@gnu.org \
--cc=jsw@wilsonjc.us \
/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).