Mercurial > pidgin

comparison libfaim/README.gaim @ 250:c5aa7bf99059

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
[gaim-migrate @ 260] Mostly just touch-ups to the README.gaim file, and a couple FIXME's thrown about in oscar.c committer: Tailor Script <tailor@pidgin.im>
author Eric Warmenhoven <eric@warmenhoven.org>
date Mon, 22 May 2000 15:43:11 +0000
parents 810c595258c8
children b1ff272bc495
comparison
equal deleted inserted replaced
249:810c595258c8 250:c5aa7bf99059
14 oscar is basically faimtest (the very instructional program included with the 14 oscar is basically faimtest (the very instructional program included with the
15 libfaim source on sourceforge) with the Gaim GTK front-end. I'll put any changes 15 libfaim source on sourceforge) with the Gaim GTK front-end. I'll put any changes
16 I make into a file, but so far, I haven't made any changes other than moving the 16 I make into a file, but so far, I haven't made any changes other than moving the
17 .h files down a directory. 17 .h files down a directory.
18 18
19 And finally, a word of warning. Gaim/Faim is VERY buggy. It'll screw with your
20 .gaimrc file. It won't always sign on right. It uses all your CPU. Please, don't
21 use this for anything other than laughs right now. Hopefully we'll get it
22 working better soon (please help!).
23
19 CURRENTLY SUPPORTED FEATURES 24 CURRENTLY SUPPORTED FEATURES
20 ============================ 25 ============================
21 Signing on 26 Signing on
22 Sending IMs 27 Sending IMs
23 Receiving IMs 28 Receiving IMs
24 Being away/coming back 29 Being away/coming back
25 Being idle 30 Being idle
26 Setting your info 31 Setting your info
27 Getting users' info 32 Getting users' info
28 Getting users' away messages (PLEASE do not use oscar/libfaim just because of 33 Getting users' away messages (PLEASE do not use oscar/libfaim just because of
29 this, gaim with libfaim still really buggy, none of you will listen to 34 this, gaim with libfaim is still really buggy, none of you will listen
30 me anyway) 35 to me anyway)
31 Telling the server who's on your permit/deny lists (buggy) 36 Telling the server who's on your permit/deny lists (buggy)
32 Chat: 37 Chat:
33 - joining rooms 38 - joining rooms
34 - leaving rooms 39 - leaving rooms
35 - talking 40 - talking
45 Changing your password 50 Changing your password
46 File transfer/IM images/voice chat/etc. 51 File transfer/IM images/voice chat/etc.
47 52
48 KNOWN ISSUES 53 KNOWN ISSUES
49 ============ 54 ============
50 - libfaim apparently has a problem with receiving messages to fast (sort of). If 55 - libfaim apparently has a problem with receiving messages too fast (sort of).
51 someone sends you a message "too fast", the server says "slow down" basically, 56 You can receive more messages in less time with TOC than with libfaim. It's not
52 and lets you know that a message was dropped. The time interval between messages 57 completely libfaim's fault though.
53 seems to be much longer with libfaim than with TOC (i.e. you can receive more
54 messages in less time with TOC than with libfaim). The outgoing limit seems to
55 be about the same. So if all your friends are slow typists, this shouldn't be a
56 problem.
57 58
58 - Signing on every once in a while acts really bizarrely for me. Maybe it's just 59 - Signing on every once in a while acts really bizarrely for me. Maybe it's just
59 me. 60 me. I think it has something to do with the horrible lack of error checking and
61 recovery on gaim's part.
60 62
61 - Adding or removing people to your permit/deny lists causes the server to tell 63 - Adding or removing people to your permit/deny lists causes the server to tell
62 you everyone on your buddy list signed off and then immediately signed in again. 64 you everyone on your buddy list signed off and then immediately signed in again.
63 While you won't ever see that it happens (other than everyone will suddenly have 65 While you won't ever see that it happens (other than everyone will suddenly have
64 the guy-in-the-door icon), you'll hear it. Be warned. 66 the guy-in-the-door icon), you'll hear it. Be warned. (This also happens at
67 sign-on, because the list gets built, even if you don't have a list.)
68
69 - It doesn't set the current_user in .gaimrc correctly, so the users listed in
70 there will get really warped. Don't worry, it's just a problem with the .gaimrc,
71 but it's an annoying one.
72
73 - Oh, yeah, by the way, it'll eat up all your CPU. (Someone please fix this,
74 there's a nice FIXME near the top of oscar.c that says what the problem is.)
65 75
66 HOW TO HELP 76 HOW TO HELP
67 =========== 77 ===========
68 So here's what you can do in order to help gaim use libfaim. There are basically 78 So here's what you can do in order to help gaim use libfaim. There are basically
69 3 steps: 79 3 steps:
114 aim_send_im(gaim_sess, gaim_conn, name, AIM_IMFLAGS_AWAY, msg); 124 aim_send_im(gaim_sess, gaim_conn, name, AIM_IMFLAGS_AWAY, msg);
115 else 125 else
116 aim_send_im(gaim_sess, gaim_conn, name, 0, msg); 126 aim_send_im(gaim_sess, gaim_conn, name, 0, msg);
117 } 127 }
118 128
119 That should be all that's needed. And that's that. Happy hacking. 129 That should be all that's needed.
130
131 There are also FIXME's scattered about oscar.c. Grep around for those, figure
132 out what needs to be fixed, do that sort of thing. :) (Fixing the things listed
133 in KNOWN ISSUES above, or any other bugs you happen to find, is a very good use
134 of your time.) (You didn't hear that from me.)