From: Linas Vepstas <linasvepstas@gmail.com>
To: Daniel Kraft <d@domob.eu>
Cc: guile-user@gnu.org
Subject: Re: calling scheme procedures by name from C
Date: Sun, 2 Aug 2009 15:07:35 -0500 [thread overview]
Message-ID: <3ae3aa420908021307n3df631f6l6c66a816e4112776@mail.gmail.com> (raw)
In-Reply-To: <4A75EB0D.2060805@domob.eu>
2009/8/2 Daniel Kraft <d@domob.eu>:
>> Yeah, X examples are rather anachronistic. I dunno, an OpenGL
>> version might be fun. Imagine .. 3D programming in scheme ..!
>> it would not be a bad idea, I don't think.
>
> Hm... Maybe allowing to build a simple 3D scene, like:
>
> (define x (make-scene))
> (add-sphere x '(1 2 3) 5 'red)
> ...
>
> But I fear this makes the backend code a lot more complicated than is good
> for this purpose; and the OpenGL code probably gets also lengthier than the
> X one (though I'm not an expert with OpenGL).
There are some very easy-to-use windowing toolkits intended for
OpenGL e.g. glut. But, yes, simply setting up lights, setting up
viewpoint, declaring basic surface properties would be verbose.
>> Anyway, doing something interactive would be appropriate --
>> something vaguely enjoyable when its done. Maybe a simple
>> fractal explorer?
>
> Fractal Explorer sounds nice, and I'd use Gtk+ as "graphics library" for it.
> On the other hand, I also quite like keeping the original "logo" package;
> with the interactive fractal explorer, I don't see much one could do with it
> apart from zooming/moving with Scheme commands. For the logo package, one
> can, for instance, quite elegantly construct a Koch curve with a recursive
> Scheme function -- I don't know if the existing tutorial does this, but I
> quite like this idea and it would give a "nice" example where scripting with
> Guile is really useful and produces a cool result.
>
> So I favour keeping it but maybe really switching the backend to Gtk+ from
> X. Or do you have some other ideas for a good example project?
Sounds good to me. Whatever excites you the most is what counts!
--linas
next prev parent reply other threads:[~2009-08-02 20:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-02 9:17 calling scheme procedures by name from C Richard Shann
2009-08-02 11:17 ` Linas Vepstas
2009-08-02 12:03 ` Richard Shann
2009-08-02 15:00 ` Mike Gran
2009-08-02 17:22 ` Linas Vepstas
2009-08-02 18:08 ` Daniel Kraft
2009-08-02 19:15 ` Linas Vepstas
2009-08-02 19:37 ` Daniel Kraft
2009-08-02 20:07 ` Linas Vepstas [this message]
2009-08-13 23:19 ` Updated Guile Tutorial Neil Jerram
2009-08-02 13:00 ` calling scheme procedures by name from C Paul Emsley
2009-08-02 13:35 ` Richard Shann
2009-08-02 19:51 ` Peter TB Brett
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=3ae3aa420908021307n3df631f6l6c66a816e4112776@mail.gmail.com \
--to=linasvepstas@gmail.com \
--cc=d@domob.eu \
--cc=guile-user@gnu.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).