caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Oliver Bandel <oliver@first.in-berlin.de>
To: OCaml <caml-list@inria.fr>
Subject: [Caml-list] LablGtk-documentation...
Date: Thu, 17 Sep 2015 10:27:18 +0200	[thread overview]
Message-ID: <20150917102718.Horde.e0qQZzgq3rVrjG81WbumTBv@webmail.in-berlin.de> (raw)

Hello,

possibly some people who are responsible for the LablGtk-documentation  
are reading here on this list.

The ressources are spread over different documents, and these documents
contain a lot of broken links.

What seems to be the main page for LablGtk, IMO, is this one:

http://lablgtk.forge.ocamlcore.org/


There are links to API-descriptions as well as a README and tutorials.


  1
===
Let's look at the API-documentation:
   http://lablgtk.forge.ocamlcore.org/refdoc/index.html

Nice to have that document. But the links to GtK (C-API) are not available.

Example: http://lablgtk.forge.ocamlcore.org/refdoc/GEdit.html
If you look for "val entry_completion" there is a linkt to the  
documentation of
"GtkEntryCompletion".
But that link is the following:  
"file:///usr/share/gtk-doc/html/gtk/GtkEntryCompletion.html"
and thats, why the document is not avaialable.

I think, it would be much better to have detailed information inside the
API-description itself (instead of comparing LablGtk/OCaml and GtK/C  
documentation),
but as long as that is not the case, the link to GtK itself would be better
than not to have such a link.

So it would be nice, to make these links avaialable.

  2
===
Let's look at the "LablGtk2 Tutorial by SooHyoung Oh", which is very  
helpful, btw.
But it suffers from the same broken-link desease.

Example:  
http://plus.kaist.ac.kr/~shoh/ocaml/lablgtk2/lablgtk2-tutorial/x459.html
There is a link to "GPack.table"-documentation.
But following the link gives "Server not found".
So, izt seems the document has changed it's location a while ago,
and the links weren't updated in the document.


  3
===
Let's look at the "Treeview Tutorial by SooHyoung Oh", which I did not  
explored
in depth so far. But just testing for broken links, arbitrarily picking a page
immediately also brought a broken link.

Example:  
http://plus.kaist.ac.kr/~shoh/ocaml/lablgtk2/treeview-tutorial/ch03s05.html
The link to the "get" method gives "Server not found", and the link to  
"gtk_tree_model_get"
gives document not found.

(Looks like the Gnome-documents have changed location.)


These are just some examples.
I assume there will be more issues to find.

I would like to ask the people, who maintain these documents,
to fix these (and possibly other) issues, so that the quality of the
documentation could become better.

Also, if there are other docs abozt GtK/LablGtk, it would be nice if  
they could be added
to the above mentioned main page, so that these other docs are  
available easily.


Thanks In Advance,
     Oliver



             reply	other threads:[~2015-09-17  8:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-17  8:27 Oliver Bandel [this message]
2015-12-03  1:15 ` Hendrik Boom
2015-12-03 20:14   ` Adrien Nader
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=20150917102718.Horde.e0qQZzgq3rVrjG81WbumTBv@webmail.in-berlin.de \
    --to=oliver@first.in-berlin.de \
    --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).