Mercurial > pidgin
view libfaim/README.gaim @ 268:f8a29745247c
[gaim-migrate @ 278]
Two star college football players need to pass the final to play in the big
game. The professor loves football, but knows these guys aren't the brightest
bulbs in teh box, so he gives them a special final, puts them in a room by
themselves, and gives them an hour.
The guys look at each other, and start in on the final, which has only one
question: "What did Old MacDonald have?"
One guy looks at the other and says, "Do you know the answer to this?"
The other guy says, "Duh, a farm."
"How do you spell that?"
"Stupid! EIEIO!"
committer: Tailor Script <tailor@pidgin.im>
author | Eric Warmenhoven <eric@warmenhoven.org> |
---|---|
date | Thu, 25 May 2000 18:58:21 +0000 |
parents | 59f1748b09a6 |
children | cfa39d39dec6 |
line wrap: on
line source
Hello, your good friend EW here with a nice little notice that I'm sure will affect the ten of you who actually read this. I'm going to start trying to get gaim to use Oscar through libfaim. As far as I can tell, the only thing it used to be able to do is sign on and receive IMs. I updated libfaim to what's currently in the libfaim CVS on sourceforge. As of right now, I've been able to implement most of the features libfaim offers. I'm going to try to make as few modifications as possible to the libfaim code. The only two modifications I'll probably ever make to it are 1) to make my life easier (like putting all the .h files in the same directory as the .c files) or 2) to fix a compilation error that I happen to be able to fix very easily (like with a typo or something). That means that what you're getting when you enable oscar is basically faimtest (the very instructional program included with the libfaim source on sourceforge) with the Gaim GTK front-end. I'll put any changes I make into a file, but so far, I haven't made any changes other than moving the .h files down a directory. And finally, a word of warning. Gaim/Faim is VERY buggy. It'll screw with your .gaimrc file. It won't always sign on right. It uses all your CPU. Please, don't use this for anything other than laughs right now. Hopefully we'll get it working better soon (please help!). CURRENTLY SUPPORTED FEATURES ============================ Signing on Receiving IMs Sending IMs Being idle Being away/coming back Setting your info Getting users' info Chat: - joining rooms - leaving rooms - talking - getting invited - inviting someone Getting users' away messages (PLEASE do not use oscar/libfaim just because of this, gaim with libfaim is still really buggy, none of you will listen to me anyway) Telling the server who's on your permit/deny lists CURRENTLY UNSUPPORTED FEATURES ============================== Warning users/getting warned Chat: - whispering - refreshing the chatlist in the preferences dialog Getting/setting dir info Changing your password File transfer/IM images/voice chat/etc. KNOWN ISSUES ============ - libfaim apparently has a problem with receiving messages too fast (sort of). You can receive more messages in less time with TOC than with libfaim. It's not completely libfaim's fault though. - There are a lot of problems with panel support (funny that I'm supporting the panel code, and the oscar code I wrote doesn't work well with it). I think this is related to oscar_callback being funny. - Oscar doesn't do whispering in chat rooms any more (and hasn't for quite a while, evidently). So if you want to "whisper" to someone, just IM them. - Oh, yeah, by the way, it'll eat up all your CPU. (Someone please fix this, there's a nice FIXME near the top of oscar.c that says what the problem is.) - There are also FIXME's scattered about oscar.c. Grep around for those, figure out what needs to be fixed, do that sort of thing. :) (Fixing the things listed in KNOWN ISSUES above, or any other bugs you happen to find, is a very good use of your time.) (You didn't hear that from me.)