caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Adrien Nader <adrien@notk.org>
To: Hendrik Boom <hendrik@topoi.pooq.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] LablGtk-documentation...
Date: Thu, 3 Dec 2015 21:14:35 +0100	[thread overview]
Message-ID: <20151203201435.GA10777@notk.org> (raw)
In-Reply-To: <20151203011510.GA21969@topoi.pooq.com>

Hi,

For the C API, you should probably just load
https://developer.gnome.org/gtk2/stable/ and keep it around: the
documentation tends to not "regress" and it's often useful to have the
most recent one so that you can see that an API that you might need is
available in a newer version.

As you've probably seen, the C API links are file:/// URIs. This means
they're neither wrong nor right: it depends on the machine used to
display the documentation. I cannot tell what is the major on-disk path
for that documentation. For some people it would be solved by installing
the corresponding distribution package.

You can definitely argue that the links should point to gnome.org or
gtk.org but the issue remains: they point to an external resource which
is free to change. In any case, I agree that this should be fixed but I
don't have a definitive answer about how.

I'm partly to blame because I had started with lablgtk but subsequently
mostly gave up on GTK+ (not lablgtk) and therefore don't practice it.
Technically-speaking, I could fix it but I wouldn't be dog-feeding it,
making changes risky. Anyway, if you're interested in contributing, your
involvement will be welcome and I'll make my best to help you with that
(off-list preferably for simplicity matters).

-- 
Adrien Nader

  reply	other threads:[~2015-12-03 20:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-17  8:27 Oliver Bandel
2015-12-03  1:15 ` Hendrik Boom
2015-12-03 20:14   ` Adrien Nader [this message]
2015-12-03 20:52     ` Hendrik Boom

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=20151203201435.GA10777@notk.org \
    --to=adrien@notk.org \
    --cc=caml-list@inria.fr \
    --cc=hendrik@topoi.pooq.com \
    /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).