On Sun, 03 Feb 2008 18:40:37 +0200
Stefan Kost <[EMAIL PROTECTED]> wrote:
> > - Are those docs maybe declared unaccessible by the spider engines?
> > (by robots.txt or so)
>
> I guess library.gnome.org is just too new and maybe not linked that
> much yet (I used good to search for sites that li
Hi,
John Coppens schrieb:
> 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 ot
> > - Is something in the google algorithms preferencial to anything but C?
In a way, yes. It's impossible to make C-specific queries because a single C
in the query is either ignored, or machtches pretty much the entire WWW. And
C API docs seldom mention the fact that they're intended to be used
ate: Wed, 30 Jan 2008 17:27:33 -0200
> From: John Coppens <[EMAIL PROTECTED]>
> Subject: What's wrong with the docs?
> To: gtk-app-devel-list@gnome.org
> Message-ID: <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset=US-ASCII
>
> Hello all...
>
> Ther
On Jan 30, 2008 2:27 PM, John Coppens <[EMAIL PROTECTED]> wrote:
> 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
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 i
