From: Oliver Bandel <oliver@first.in-berlin.de>
To: John Max Skaller <skaller@ozemail.com.au>
Cc: Tim Freeman <tim@fungible.com>,
willb@cs.wisc.edu, stf@apl.it, caml-list@inria.fr
Subject: Re: [Caml-list] OCamlSDL
Date: Tue, 23 Apr 2002 16:50:40 +0200 (MET DST) [thread overview]
Message-ID: <Pine.LNX.3.95.1020423164703.462B-100000@first.in-berlin.de> (raw)
In-Reply-To: <3CC34396.9000909@ozemail.com.au>
On Mon, 22 Apr 2002, John Max Skaller wrote:
> Tim Freeman wrote:
>
> >Will Benton allegedly wrote:
> >
> >> 2. O'Caml bindings are already available for OpenGL.
> >>
> >
> >From: John Max Skaller <skaller@ozemail.com.au>
> >
> >>In that case, why are we sticking with Tk?
> >>
> >
> >I don't get it. Tk is about 2D graphics, and OpenGL is about
> >accelerated 3d graphics. Your question presupposes that we have a
> >choice between one and the other, but I can't think of any
> >applications for which that is true.
> >
> Gee, I always though 2D was a subspace of 3D...
Tk is designed for interactive GUI-Applications. And, yes,
it provides graphical output with the canvas-widget.
But I think that OpenGL is designed for having 3D-animations
and similar stuff, and not to put buttons on the screen,
on which the user can click.
And I think you have to reinvent the "button-wheel" in OpenGL.
Maybe it would be a good idea to marriage OpenGL and Tk,
so that Tk provides easy GUI-design and OpenGL provides
powerful 3D-capabilities.
Maybe there should be a GUI-Lib for OpenGL, or a 3D-canvas-
widget for Tk (OpenGL-canvas for Tk).
Ciao,
Oliver
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2002-04-23 15:10 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-18 14:32 Luc Mazardo
2002-04-18 22:03 ` Warp
2002-04-19 15:49 ` John Max Skaller
2002-04-19 15:58 ` Warp
2002-04-19 16:06 ` Will Benton
2002-04-19 16:13 ` Stefano Lanzavecchia
2002-04-19 16:27 ` Will Benton
2002-04-19 17:20 ` Warp
2002-04-20 9:06 ` John Max Skaller
2002-04-20 12:22 ` Tim Freeman
2002-04-20 12:51 ` Sven
2002-04-22 6:55 ` Tom
2002-04-22 20:05 ` John Max Skaller
2002-04-21 22:56 ` John Max Skaller
2002-04-22 6:53 ` William Chesters
2002-04-23 14:50 ` Oliver Bandel [this message]
2002-04-23 15:12 ` Stefano Lanzavecchia
2002-04-24 1:00 ` Jacques Garrigue
2002-04-24 1:07 ` John Max Skaller
2002-04-24 7:02 ` Sven
2002-04-24 9:04 ` John Max Skaller
2002-04-24 9:31 ` Sven
2002-04-24 9:42 ` Jérôme Marant
2002-04-24 11:00 ` Jérôme Marant
2002-04-29 10:11 ` Sven
2002-04-24 16:56 ` Oliver Bandel
2002-04-19 17:16 ` Warp
2002-04-19 17:45 ` Sven
2002-04-19 18:01 ` Warp
2002-04-19 18:55 ` Vincent Foley
2002-04-20 6:33 ` Alan Schmitt
2002-04-20 12:16 ` Sven
2002-04-20 9:19 ` John Max Skaller
2002-04-20 12:19 ` Sven
2002-04-20 14:47 ` Vitaly Lugovsky
2002-04-20 9:01 ` John Max Skaller
2002-04-21 12:13 ` Oliver Bandel
2002-04-21 12:27 ` Oliver Bandel
2002-04-24 14:02 Damien Doligez
2002-04-24 14:37 ` Christophe Raffalli
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=Pine.LNX.3.95.1020423164703.462B-100000@first.in-berlin.de \
--to=oliver@first.in-berlin.de \
--cc=caml-list@inria.fr \
--cc=skaller@ozemail.com.au \
--cc=stf@apl.it \
--cc=tim@fungible.com \
--cc=willb@cs.wisc.edu \
/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