Mercurial > pidgin
comparison libfaim/README.gaim @ 283:0f14e6d8a51b
[gaim-migrate @ 293]
- Good fun things here. Sometimes I think Adam does things just to make
it difficult for me, I swear (j/k :) ).
- I moved all the .h files into the faim/ directory because I'm tired
of changing faim/aim.h to just aim.h every time Adam makes an update.
- libfaim can now send messages much longer than WinAIM or TOC can. But,
the length checking code is still in conversation.c, and I haven't
changed it yet, mostly because I'm lazy.
committer: Tailor Script <tailor@pidgin.im>
author | Eric Warmenhoven <eric@warmenhoven.org> |
---|---|
date | Wed, 31 May 2000 03:20:11 +0000 |
parents | 7b06ba09ffe2 |
children | 6e609d42f767 |
comparison
equal
deleted
inserted
replaced
282:918db59d3814 | 283:0f14e6d8a51b |
---|---|
6 updated libfaim to what's currently in the libfaim CVS on sourceforge. As of | 6 updated libfaim to what's currently in the libfaim CVS on sourceforge. As of |
7 right now, I've been able to implement most of the features libfaim offers. | 7 right now, I've been able to implement most of the features libfaim offers. |
8 | 8 |
9 I'm going to try to make as few modifications as possible to the libfaim code. | 9 I'm going to try to make as few modifications as possible to the libfaim code. |
10 The only two modifications I'll probably ever make to it are 1) to make my life | 10 The only two modifications I'll probably ever make to it are 1) to make my life |
11 easier (like putting all the .h files in the same directory as the .c files) or | 11 easier or 2) to fix a compilation error. That means that what you're getting |
12 2) to fix a compilation error that I happen to be able to fix very easily (like | 12 when you enable oscar is basically faimtest (the very instructional program |
13 with a typo or something). That means that what you're getting when you enable | 13 included with the libfaim source on sourceforge) with the Gaim GTK front-end. |
14 oscar is basically faimtest (the very instructional program included with the | 14 I'll put any changes I make into a file. So far the few changes I've made have |
15 libfaim source on sourceforge) with the Gaim GTK front-end. I'll put any changes | 15 been to make a few printf's not print, and removing a few defines from a .h and |
16 I make into a file, but so far, I haven't made any changes other than moving the | 16 putting them in the Makefile/build process. |
17 .h files down a directory. | |
18 | 17 |
19 And finally, a word of warning. Gaim/Faim is VERY buggy. Please, don't use this | 18 And finally, a word of warning. Gaim/Faim is VERY buggy. Please, don't use this |
20 for anything other than laughs right now. Hopefully we'll get it working better | 19 for anything other than laughs right now. Hopefully we'll get it working better |
21 soon (please help!). | 20 soon (please help!). |
21 | |
22 I think I'm ready to start dealing with bugs being reported against it now | |
23 though. If you're going to report a bug, please check first that a) you're using | |
24 the to-the-second absolute latest CVS version, b) it's not in the unsupported | |
25 features/known issues lists below, c) someone hasn't already reported the bug on | |
26 sourceforge (please check BOTH the open and closed bugs), and finally d) that | |
27 you can reproduce it. | |
28 | |
29 Also, please *don't* IM me about a bug, as I have a tendency to forget things | |
30 like that. Reporting it on sourceforge is a much better way of reporting bugs, | |
31 because then other people can see that the bug is already known, and it's harder | |
32 for me to forget. | |
22 | 33 |
23 CURRENTLY SUPPORTED FEATURES | 34 CURRENTLY SUPPORTED FEATURES |
24 ============================ | 35 ============================ |
25 Signing on | 36 Signing on |
26 Receiving IMs | 37 Receiving IMs |
57 | 68 |
58 - Chat is really funny. I have no idea what's going on with it. I'm not sure I | 69 - Chat is really funny. I have no idea what's going on with it. I'm not sure I |
59 want to know. I'm not worried about it, I never use chat. It's not exactly high- | 70 want to know. I'm not worried about it, I never use chat. It's not exactly high- |
60 priority. | 71 priority. |
61 | 72 |
73 - The permit list sometimes has problems when you start gaim, but if you change | |
74 to it in the middle of a session there don't seem to be any problems. | |
75 | |
76 - "Allow anyone" and "Deny some" serve the same function. That's not a bug. But | |
77 "Allow anyone" works all the time (?) and "Deny some" doesn't work some of the | |
78 time. That's a bug. | |
79 | |
62 - Gaim/TOC can do file transfers, but Gaim/Faim cannot. This is not because | 80 - Gaim/TOC can do file transfers, but Gaim/Faim cannot. This is not because |
63 there is any difference in the two protocols as far as the actual transfer is | 81 there is any difference in the two protocols as far as the actual transfer is |
64 concerned. The only thing preventing this is it is currently not possible to | 82 concerned. The only thing preventing this is it is currently not possible to |
65 recognize when we've received a file transfer request using libfaim. Once | 83 recognize when we've received a file transfer request using libfaim. Once |
66 libfaim can tell us that we've received the request, the only thing we should | 84 libfaim can tell us that we've received the request, the only thing we should |