Pidgin Development

This is an introductory paragraph describing how we go about developing Pidgin. It probably just contains a lot of fluff that everyone already knows, but we have to include it because otherwise it would just be a bunch of links, and that would look weird.

First Useful Subheader

This paragraph is probably about getting the source code. That's typically a useful starting point. Maybe it explains what subversion commands to use. It problably contains a link to ​http://developer.pidgin.im/browser. It probably also contains a link to the sourceforge download pages and explains that you probably want to hack against svn.

Oh, and it has to include a list:

• Useful subversion tutorial!
• How to download subversion for Windows, maybe.
• Browse Source, again

This one is about, maybe, building?

So here, we probably go through the steps in building. It might make sense to subhead this one too, but you always have to include an introduction paragraph before doing that. They teach you that when writing a book. So that's what this paragraph is for.

Dependencies

We'll probably list the dependencies and give a list of where to get them:

• GTK+ - ​http://gtk.org
• NSS - ​http://mozilla.org
• Some other dependency - It's webpage

You get the gist.

Building on Linux

This one is easy. We just include one of those cute little "code" boxes:

./autogen
make
sudo make install
sudo ldconfig

Maybe we link to SomeOtherPage? about what happens if the build fails.

Building on Windows

I'm not even going to bother describing what might go here.

Blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah

That should suffice.

Oh, now we need to describe the API!

This is probably just another set of links!

• Link to API page
• UsefulAPITutorial?

And plugin writing

More links!

• How to write plugins!

And maybe how to use libgaim

This probably goes to some other page, UsingLibgaim?, or something. Nonetheless, we should give a brief overview of it here, perhaps. Oh, and links:

• An overview of CoreUiSplit?
• A useful tutorial creating some really simple UI can be found Here?

Useful Resources

Because I put no thought into this organization and made this shell of an outline only to make people chuckle, there are undoubtally a whole bunch of things that should go on this page that don't fit anywhere. For example:

• Subscribe to get updates about ticket items: ​http://pidgin.im/cgi-bin/mailman/listinfo/tracker
• This?
• AndThis?
• AndThat?
• AndThis?
• AndThisToo?

Oh, yeah, pimp my book out

Here I have a paragraph describing how great my book is. Maybe a picture of the cover and a link to the Amazon page.