From: Sven <luther@dpt-info.u-strasbg.fr>
To: John Max Skaller <skaller@ozemail.com.au>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] OCamlSDL
Date: Wed, 24 Apr 2002 11:31:45 +0200 [thread overview]
Message-ID: <20020424113145.A1642@dpt-info.u-strasbg.fr> (raw)
In-Reply-To: <3CC67517.4070200@ozemail.com.au>; from skaller@ozemail.com.au on Wed, Apr 24, 2002 at 07:04:23PM +1000
On Wed, Apr 24, 2002 at 07:04:23PM +1000, John Max Skaller wrote:
> >
> >
> >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.
Mmm, i understand, ...
But yyou need a widget to hold the OpenGL area or something.
You could also try doing GLU/GLX whatever directly with appropriate C stubs,
it should not be to heavy.
That said, another way would be to run OpenGL on top of fbdev, this way, you
don't even have X running, which would be nice, you could even imagine a CD
with a kernel, some drivers, and running your game directly, a bit like a
console, nice, not ?
The problem is that DRI is rather dependant on X right now, and doesn't make
provisions for someone wanting to run accelerated mesa in something which is
not X. You would need your own windows and such stuff though.
> 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.
Ok,
> 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.
Then have a look at the people working with fbdev, it should give you what
you want. This idea has been discussed various time on the linux-fbdev mailing
list (on sourceforge i think) and there are people who want things like that
there, have a look at the archive.
> 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.
A native fbdev binding would be nice also, i have proposed such a project to
my student, but nobody was interested and i lack the time to do so myself,
but then, maybe i will.
(reverting advi to use again the graphics module and having a fbdev
implementation of the graphics module would go a long step in the way of
having an easy to show without linux and advi installed presenter.
Friendly,
Sven Luther
>
> --
> 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
-------------------
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:30 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
2002-04-24 9:31 ` Sven [this message]
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=20020424113145.A1642@dpt-info.u-strasbg.fr \
--to=luther@dpt-info.u-strasbg.fr \
--cc=caml-list@inria.fr \
--cc=skaller@ozemail.com.au \
/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