[gnome-love] Doc Links [was: Re: [gnome-love]Wow.]

[Dan Mueth <d-mueth uchicago edu>]

On Tue, 22 May 2001, Matthew Walton wrote:

> The Gtk+ docs are pretty good, by the way. Good enough, anyway... but
> I've never managed to get a GNOME app up and running. Guess I need to
> spend a bit more time playing with that, learning my way around the
> GNOME libs and so forth. Is there a good place to start at with this or
> do I just trawl through the docs and the header files and some existing
> GNOME programs to see what's going on?

The GNOME developer docs are intermittant in quality and coverage.  You
will find that some docs are good, some are bad, some are obsolete, and
some don't exist yet.  (Hopefully some people on this list can help to
improve the situation.)  We hope to have all the developer documentation
updated well in advance of the GNOME 2.0 release.  Nonetheless, there is a
fair amount of good documentation to help you get started...

For an overview of the architecture, look here:
http://developer.gnome.org/arch/

For various documents, look here:
http://developer.gnome.org/doc/

What I would personally highly recommend to anybody getting started
hacking on GNOME is George Lebl's tutorials he wrote for IBM
DeveloperWorks.  You can find them here:

http://www-105.ibm.com/developerworks/papers.nsf/dw/linux-papers-byauthor?OpenDocument&Start=1&Count=500&Expand=24

If that link gives you trouble, most of them are linked from here:
http://developer.gnome.org/doc/tutorials/

API docs are here:
http://developer.gnome.org/doc/API/

And I'll repeat the book links for completeness, even though Miguel
already gave it:
http://developer.gnome.org/doc/books/

And if you are interested in non-hacking projects, the documentation for
various GNOME projects can be found in each of the project pages:
http://developer.gnome.org/projects/

Oh yeah - and if you want to contribute but you aren't sure what is the
right thing for you, look at:
http://developer.gnome.org/documents/joining-gnome/

Happy reading.  And once you get things figured out, consider writing some
developer documentation yourself.

Dan