There is a *lot* of pretty good documentation.
In per-object, per-function API documentation form:
http://developer.gnome.org/doc/API/
For gtk is mostly a community-based documenation project,
(with sgml-templates generated from the code, courtesy of Damon Chaplin),
so if you notice inadequecies feel free to report them
as patches on [EMAIL PROTECTED]
And Havoc Pennington's excellent GGAD is a book, available
freely online:
http://developer.gnome.org/doc/GGAD/
Of course, we are helpless ultimately:
people simply don't RTFM enough.
- Dave
On Tue, 18 Jan 2000, Jeroen Benckhuijsen wrote:
> Hi,
>
> As seen from many mails, often there are complains about the
> documentation of GTK. IMHO these complains are very important. From my
> own experience i can say it's very frustrating to have to dive into the
> source, to find out what a certain function does (after all, the
> intention of the toolkit is i don't have to bother about a great deal of
> functionality). Maybe this should be the first priority of the
> GTK-project: first mak sure the docs are OK. IMHO GTK is now in a stage,
> we're completion will be reached quickly, so writing the documentation
> and the tutorials should be important now. Don't get me wrong, i think
> GTK is a great toolkit, but what's a great toolkit if one does not (or
> not quite) know how to use it.
>
> Again this meant in a positive way, taken from my experiences of a GTK
> program i'm currently developing.
>
> Jeroen
>
> --
> To unsubscribe: mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
>
>
--
To unsubscribe: mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
