caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Issac Trotts <ijtrotts@ucdavis.edu>
To: caml-list@inria.fr
Subject: Re: [Caml-list] OpenGL
Date: Thu, 8 Apr 2004 13:19:09 -0700	[thread overview]
Message-ID: <20040408201909.GC13940@mev> (raw)
In-Reply-To: <200404081735.48692.jdh30@cam.ac.uk>

On Thu, Apr 08, 2004 at 05:35:48PM +0100, Jon Harrop wrote:
> On Wednesday 07 April 2004 5:07 pm, Issac Trotts wrote:
> > Did you look at LablGL?
> 
> Yes, it's lablGL that I'm working with. It's excellent for the basic stuff 
> (plotting triangles), but things quickly get quite hairy. Specifically, my 
> program needs the GLU tesselator (the reimplementation of which in ocaml is 
> prohibitively complicated). The problems with the interface provided by 
> lablGL (which can never be made to work in its current state, BTW) are 
> actually much more deep seated, and apply to lots of other parts of the 
> library.

What it is about lablGL that means it can never be made to work?
 
> There is another OpenGL interface library, IIRC, which is very low-level. 
> However, I don't like this approach as it is then easy for ocaml programs to 
> crash the OS, and stability and safety are surely two of the most important 
> advantages of ocaml.

That one is called camlgl, which seems to have been abandoned.

> I have gone some way to reimplementing the lablGL interface to the GLU 
> tesselator but it is very difficult. Not to mention the other parts of the 
> libraries which will need equivalent things done to them...

I already wrote a binding for GLU using CamlIDL, but I don't recommend
it since GLU relies so much on callbacks.  It would probably be better to
wrap Jonathan Shewchuck's Triangle code:

    http://www-2.cs.cmu.edu/~quake/triangle.html

-- 
Issac Trotts
http://mallorn.ucdavis.edu/~ijtrotts
(w) 530-757-8789

-------------------
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


  reply	other threads:[~2004-04-08 20:20 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-08 15:11 Jon Harrop
2004-04-07 16:07 ` Issac Trotts
2004-04-08 16:35   ` Jon Harrop
2004-04-08 20:19     ` Issac Trotts [this message]
2004-04-08 20:46       ` [Caml-list] Re: Triangle (was: OpenGL) Christophe TROESTLER
2004-04-08 22:25       ` [Caml-list] OpenGL Jon Harrop
2004-04-09  1:45         ` Brian Hurt
2004-04-09  2:57           ` Brandon J. Van Every
2004-04-09 10:57           ` Jon Harrop
2004-04-09 16:12             ` Brian Hurt
2004-04-10  4:32               ` Brandon J. Van Every
2004-04-10  4:59                 ` Kenneth Knowles
2004-04-10  8:17                 ` Nicolas Cannasse
2004-04-11  6:20                 ` Brian Hurt
2004-04-11  8:10                   ` skaller
2004-04-11  9:23                   ` Brandon J. Van Every
2004-04-11 12:08                     ` Jon Harrop
2004-04-11 12:01                   ` Jon Harrop
2004-04-09 12:52         ` Issac Trotts
2004-04-08 16:37   ` Anil Madhavapeddy

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=20040408201909.GC13940@mev \
    --to=ijtrotts@ucdavis.edu \
    --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;
as well as URLs for NNTP newsgroup(s).