From: John Max Skaller <skaller@ozemail.com.au>
To: caml-list@inria.fr
Subject: Re: [Caml-list] OCamlSDL
Date: Wed, 24 Apr 2002 19:04:23 +1000 [thread overview]
Message-ID: <3CC67517.4070200@ozemail.com.au> (raw)
In-Reply-To: <20020424090250.A32612@dpt-info.u-strasbg.fr>
>
>
>Wellm maybe i don't understand you, but the lablgl binding already provide a
>way to do OpenGL in Tk (using the togl widget) and the lablgtk bindings
>provide a way to do OpenGL in gtk+ using the gtkglarea widget.
>
>What do you want more ?
>
Nothing. I want LESS. I do NOT want Tk there, nor Gtk.
And for a game, not even the window manager.
I have a friend committed to using OpenGL to do a game.
He's NOT interested in widgets or window managers
from some toolkit. He'll program the buttons to behave
exactly as he want them too directly with the low
level graphics interfaces.
I want to implement a new kind of window manager
called HWM. I can't even host it on X (except at low level)
since X's idea of a WM is archaic and precisely what
I'm trying to replace.
So neither of us is remotely interested in hosting
OpenGL inside a widget of some brain dead toolkit
living inside some brain dead window manager.
We want to use Open GL to REPLACE these
components.
Ideally, Ocaml would have an OpenGL interface
with a binding which works inside the native
window manager (in a window -- for testing) but
which could be replaced by another binding (transparently)
which took over the whole screen, either
directly (for performance) or via low level primitives
of the native system (X windows etc) for hosting
within an existing environment.
So for example, on Linux, I'd want a Mesa binding.
--
John Max Skaller, mailto:skaller@ozemail.com.au
snail:10/1 Toxteth Rd, Glebe, NSW 2037, Australia.
voice:61-2-9660-0850
-------------------
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-24 9:04 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
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 [this message]
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=3CC67517.4070200@ozemail.com.au \
--to=skaller@ozemail.com.au \
--cc=caml-list@inria.fr \
/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