view README.CVS @ 6122:914f2d5da21c

[gaim-migrate @ 6596] Fix 2 compiler warnings. Make auto-login for IRC accounts without passwords work. Thanks to Luke for finding this and making a kick-assingly correct guess as to the cause. Fix the MSN sign-off-infinite-loops-after-getting-info-about-mail bug. Fix "Yahoo smilies for the "angel" smiley are incorrect" http://sourceforge.net/tracker/index.php?func=detail&aid=728663&group_id=235&atid=100235 Fix a bug that I introduced yesterday freaking afternoon. I would have commited the fix yesterday, but SF CVS was not working. <faceprint> KingAnt: you just broke the ticker <KingAnt> faceprint: How so? <KingAnt> Oh, event_signon? <faceprint> the ticker is what needs event_buddy_signon to get called twice <faceprint> i don't know what is the right behavior, but i'm in bootloader hell, just thought i'd alert you <KingAnt> faceprint: So that it doesn't always show people with the open door? <faceprint> KingAnt: right I just added an ugly little timeout that updates the icon after 11 seconds. The icon in the blist gets updated after 10. committer: Tailor Script <[e-mail]>

If you plan to use gaim CVS, PLEASE read this message in its entirety!

Gaim is a fast-moving project with a regular release schedule.  Due to
the rate of gaim development, CVS undergoes frequent bursts of massive
changes, often leaving behind brokenness and partial functionality
while the responsible developers rewrite some portion of code or seek
to add new features.

What this all boils down to is that CVS _WILL_ sometimes be broken.
Because of this, we ask that users who are not interested in
personally tracking down bugs and fixing them (without a lot of
assistance from the developers!) avoid CVS and use releases.  Since
releases will be made often, this should not prevent anyone from using
the newest, shiniest features -- but it will prevent users from having
to deal with ugly development bugs that we already know about but
haven't gotten around to fixing.

I you are interested in hacking on gaim, please read README and
HACKING, and take note of the issues in PROGRAMMING_NOTES.  (Note that
they may be somewhat out of date at times.) Win32 developers, please
read README.mingw.

By far the best documentation, however, is the documented code.  Not
all parts of gaim have yet been documented, but the major subsystems
are falling fast.  If you have doxygen, you can use the Doxyfile in
the toplevel directory to generate pretty documentation.  Otherwise
(or even if you do!), the header files for each subsystem contain
documentation for the functions they contain.  For instance,
conversation.h contains documentation for the entire
gaim_conversation_* API, and account.h contains documentation for the
gaim_account_* API.

If you have questions, please feel free to contact the gaim developers
by email at [e-mail], on IRC at
irc.freenode.net in #gaim, or via the sourceforge forums at
http://www.sourceforge.net/projects/gaim.  Please do as much homework
as you can before contacting us; the more you know about your
question, the faster and more effectively we can help you!

Send patches to [e-mail] or post them in the
Sourceforge forums at http://www.sourceforge.net/projects/gaim.