Re: What's wrong with the docs?

[Thomas Stover <thomas wsinnovations com>]

I feel the same way. I can't think of an example off of the top of my 
head, but I swear there have been things that the only way I figured 
them out was by reading the python documentation and sort of guessing at 
the C API. Yes I look at the reference docs on gtk.org and gnome.org.
> Date: Wed, 30 Jan 2008 17:27:33 -0200
> From: John Coppens <john jcoppens com>
> Subject: What's wrong with the docs?
> To: gtk-app-devel-list gnome org
> Message-ID: <20080130172733 d9903428 john jcoppens com>
> Content-Type: text/plain; charset=US-ASCII
>
> Hello all...
>
> There must be something terribly wrong somewhere, when I try to find
> documentation on operation with GTK+ or GDK elements, I always seem to
> get _much_ more documentation from the Python/Perl libraries than from
> the actual C interface. I'm sure others noticed the same trend.
>
> So, why is this?
>
> - Are the original (C/C++) docs really so scarse they don't appear at
>   the top of of the list? or...
>
> - Is something in the google algorithms preferencial to anything but C?
>
> - Are those docs maybe declared unaccessible by the spider engines?
>   (by robots.txt or so)
>
> - Or are those alternative languages just much more popular than C?
>
> Which makes this question pop up: Wouldn't it be interesting/practical
> to have _common_ documentation. Say, GtkWidget is used in Python like
> this, in C like this, etc.? I could even serve as an educational tool
> to compare languages.
>
> Just idle thoughts...
>
> John
>
>