Mercurial > pidgin
annotate README.CVS @ 9460:eae7e049d639
[gaim-migrate @ 10285]
" This patch completely eliminates the use of the old
numeric prpl identifiers.
I've noticed that some plugins (both in gaim's cvs and
external) continue to use the constants even though
they are essentially no longer valid - code that relies
on them being unique will fail - the new built-in prpls
(SILC and novell) ,and any recent external prpls don't
have numeric values.
The once side effect that the removal causes is that
the code for importing of the old .gaimrc and *.blist
files is a little more kludgy (using magic numbers
instead of the old constants). IMHO this isn't a big
deal as the code will go away eventually anyway.
**This patch also fixes the raw plugin so that i
compiles once again.
**Someone should make sure that the gaim-remote and raw
plugins still work. (If the raw doesn't work, it may be
unrelated as it hasn't been updated since the latest
significant MSN changes - i just made a minor change to
make it compile)" --Daniel Atallah
(13:44:44) Me: what think you of getting rid of prpl numbers?
(13:45:05) Sean: what do you mean?
(13:45:27) Me: right now they are listed as deprecated, but still used in a
few of our own plugins as well as in some 3rd party stuff
(13:45:32) Me: and the enum still exists in the core
(13:45:44) Me: and the newwer prpls such as novell don't use them
(13:45:59) Me: datallah has submitted a patch to get rid of them entirely
(13:46:31) Me: the only thing it would break would be the old blist import,
which he hacked into working with magic numbers, but which i tend to think
we could remove entirely anyway
(13:50:03) Sean: Let's get rid of them, then.
(13:50:10) Sean: and take out old .blist code too
(13:50:14) Me: cool
(13:52:37) Sean: we should get rid of .gaimrc code too, sometime.
(13:53:02) Sean: If anyone's seriously just now upgrading from 0.59.x, or
whatever, they deserve to lose their preferences.
(12:27:56) LSchiere: Paco-Paco: what do you think of getting rid of the
deprecated prpl numbers?
(12:28:14) Paco-Paco: LSchiere: I think it shouldh ave happened long ago
committer: Tailor Script <tailor@pidgin.im>
author | Luke Schierer <lschiere@pidgin.im> |
---|---|
date | Tue, 06 Jul 2004 18:06:43 +0000 |
parents | 17a446f5e99b |
children | e4a27c9aec4c |
rev | line source |
---|---|
5640 | 1 If you plan to use gaim CVS, PLEASE read this message in its entirety! |
2 | |
6798 | 3 Gaim is a fast-moving project with a somewhat regular release schedule. |
6797 | 4 Due to the rate of gaim development, CVS undergoes frequent bursts of |
5 massive changes, often leaving behind brokenness and partial | |
6 functionality while the responsible developers rewrite some portion of | |
7 code or seek to add new features. | |
5640 | 8 |
9 What this all boils down to is that CVS _WILL_ sometimes be broken. | |
10 Because of this, we ask that users who are not interested in | |
11 personally tracking down bugs and fixing them (without a lot of | |
12 assistance from the developers!) avoid CVS and use releases. Since | |
13 releases will be made often, this should not prevent anyone from using | |
14 the newest, shiniest features -- but it will prevent users from having | |
15 to deal with ugly development bugs that we already know about but | |
16 haven't gotten around to fixing. | |
17 | |
6246 | 18 If you are interested in hacking on gaim, please read README and |
5640 | 19 HACKING, and take note of the issues in PROGRAMMING_NOTES. (Note that |
20 they may be somewhat out of date at times.) Win32 developers, please | |
21 read README.mingw. | |
22 | |
23 By far the best documentation, however, is the documented code. Not | |
24 all parts of gaim have yet been documented, but the major subsystems | |
25 are falling fast. If you have doxygen, you can use the Doxyfile in | |
26 the toplevel directory to generate pretty documentation. Otherwise | |
27 (or even if you do!), the header files for each subsystem contain | |
28 documentation for the functions they contain. For instance, | |
29 conversation.h contains documentation for the entire | |
30 gaim_conversation_* API, and account.h contains documentation for the | |
31 gaim_account_* API. | |
32 | |
33 If you have questions, please feel free to contact the gaim developers | |
34 by email at gaim-devel@lists.sourceforge.net, on IRC at | |
35 irc.freenode.net in #gaim, or via the sourceforge forums at | |
36 http://www.sourceforge.net/projects/gaim. Please do as much homework | |
37 as you can before contacting us; the more you know about your | |
38 question, the faster and more effectively we can help you! | |
39 | |
40 Send patches to gaim-devel@lists.sourceforge.net or post them in the | |
41 Sourceforge forums at http://www.sourceforge.net/projects/gaim. |