From: Matt Gushee <mgushee@havenrock.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] OpenGL support in LablGTK2?
Date: Wed, 26 Jan 2005 22:16:11 -0700 [thread overview]
Message-ID: <41F8791B.1040600@havenrock.com> (raw)
In-Reply-To: <20041231.183021.102493377.garrigue@math.nagoya-u.ac.jp>
Hello, Jacques--
I owe you thanks for your patient response to my somewhat grouchy
questioning. Sorry about the long delay; I just haven't been dealing
well with e-mail lately.
Jacques Garrigue wrote:
> Then something will have to be done about it at that time.
> But this has been the situation for already a few years, and
> gtkglarea2 is still working, so this doesn't seem a big concern.
> Note also that the great thing about free software is that anybody is
> allowed to fix a problem when it arises.
I certainly know that. Unfortunately, the people affected most by a
problem aren't always in the best position to fix it. I guess I was
frustrated because I would like to provide a complete package, and it
happens that the problematic component is one that I really don't
understand well.
> You just have to create a gtkglarea2 package together with the
> lablgtk2 package.
I will probably provide gtkglarea as part of the lablgtk2 package. I
don't think it's good policy to introduce new Linux packages whose
upstream source is no longer maintained.
> Not a big deal. Much less work than writing an
> interface for gtkglext and all the compatibility bindings (the
> compatibility bindings are the painful part.)
I don't doubt it, and in principle I have always been a strong advocate
of backwards compatibility. But in this case I wonder (as mentioned in
an earlier post) how much it really matters. Are there in fact
significant projects using LablGTK2 with OpenGL?
> I'm satisfied that the situation is not as bad as I feared.
Thanks for the clarification.
> Note that some configurations breaking with gtk is not an unusual
> event.
Oh, yes, an old familiar story. Back around '98 or '99 I got very
annoyed at the GTK development team: it seemed about once a month they
would release a new "must-have" version that would break half the
applications on my system, including--most ironically--the GIMP. Things
have settled down a good deal since then.
--
Matt Gushee
Englewood, CO, USA
next prev parent reply other threads:[~2005-01-27 5:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-06 22:21 Matt Gushee
2004-12-07 0:28 ` [Caml-list] " Olivier Andrieu
2004-12-07 1:11 ` Matt Gushee
2004-12-07 9:51 ` Olivier Andrieu
2004-12-07 18:30 ` Matt Gushee
2004-12-07 21:36 ` Sven Luther
2004-12-08 0:33 ` Jacques Garrigue
2004-12-08 1:03 ` Matt Gushee
2004-12-08 10:03 ` Sven Luther
2004-12-08 13:53 ` Jacques Garrigue
2004-12-08 15:38 ` Sven Luther
2004-12-08 15:50 ` Sven Luther
2004-12-08 20:34 ` Grégory Guyomarc'h
2004-12-09 0:36 ` Jacques Garrigue
2004-12-09 14:17 ` Sven Luther
2004-12-24 1:56 ` Jacques Garrigue
2004-12-30 7:32 ` Matt Gushee
2004-12-31 9:30 ` Jacques Garrigue
2005-01-27 5:16 ` Matt Gushee [this message]
2005-01-27 7:59 ` Jon Harrop
2005-01-27 10:24 ` Jon Harrop
2004-12-07 10:10 ` malc
2004-12-07 15:30 ` briand
2004-12-07 18:24 ` Matt Gushee
2004-12-07 18:48 ` Blair Zajac
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=41F8791B.1040600@havenrock.com \
--to=mgushee@havenrock.com \
--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