Mercurial > pidgin
view README @ 23638:1c50f12b1c52
2008.08.02 - csyfek <csyfek(at)gmail.com>
* Commit to Pidgin
* Tickets:
Fixes #1861
Fixes #1902
References #5112
2008.08.02 - ccpaging <ecc_hy(at)hotmail.com>
* Store all keys and md5 values of qq_data in char[QQ_KEY_LENGTH]
* Use random value in inikey
* TEA header padding in crypt.c
* Rewrite login part of qq_process
2008.07.31 - ccpaging <ecc_hy(at)hotmail.com>
* Fixed: send reply when get duplicate server command. The server may not get our reply before.
* Tag custom picture as text "(Broken)"
2008.07.30 - ccpaging <ecc_hy(at)hotmail.com>, csyfek <csyfek(at)gmail.com>
* Change some debug message
* Modify buddy status flag according to eva for QQ2006
* Modify buddy status parse and correspond to eva2
* Add getIP/putIP functions to packet_parse.c, and replace some gen_ip_str
* Replace guint32 *ip with struct in_addr, and reduce g_new/g_free operation
* Source file changed:
Merge buddy_status into buddy_list
Change login_logout to qq_base
Merge keep_alive into qq_base
New qq_process extract from qq_network
* Fixed: Byte alignment bug in crypt.c, tested in ARM PDA
* Fixed: group chat message may get in before getting group info, and so group info is empty
* Add qq_send_cmd_group_get_group_info when joined a group chat in group_im.c
* Add some new group command identify according eva but further program
* Add some new QQ client version identify
* Fixed: Identify buddy's client version by IM packet, and not by status
* Add some new info in buddy's tooltip text
* Add video falg to buddy's emblem. But those flag in buddy status may not prasing correctly
* Use new timeout function to handle send keep_alive, resend packet, update buddy status
* Add new advanced options:
The end user may change interval of keep_alive, resend packet, update buddy status to feed their
need.
For example, saving network flow when use mobile phone.
Keep alive packet must be sent in 60-120 seconds whatever client rcved data of not.
The intervals of keep alive and update status should be multiple of resend's interval,
Since we use counter not time() in a single timeout function for efficiency.
* Rewrite qq_trans.c, and use one g_list to manage:
Store server packet before login, and prase all of them when get login
Store client send packet for resend scanning, confirm server reply, filter duplicate server reply
Store server packet for filter out duplicate
* Add QQ_MSG_SYS_NOTICE = 0x06 in sys_msg.c
* Rewrite qq_proc_cmd_reply and qq_proc_cmd_server:
In QQ protocol, one packet reply may need a new packet send later.
We may call it packet trigger. The triggers always is hided in every qq_process_reply.
Now we try to extract those triggers and put into a single function,
and then every trigger should be obviously and easy to manage.
author | SHiNE CsyFeK <csyfek@gmail.com> |
---|---|
date | Sat, 02 Aug 2008 15:00:46 +0000 |
parents | 56042b2f8b64 |
children |
line wrap: on
line source
Purple, Pidgin and Finch ======================== See AUTHORS and COPYRIGHT for the list of contributors. libpurple is a library intended to be used by programmers seeking to write an IM client that connects to many IM networks. It supports AIM, ICQ, XMPP, MSN and Yahoo!, among others. Pidgin is an graphical IM client written in C which uses the GTK+ toolkit. Finch is a text-based IM client written in C which uses the ncurses toolkit. These programs are not endorsed by, nor affiliated with, AOL nor any other company in any way. BUILD ===== Read the 'INSTALL' file for more detailed directions. These programs use the standard ./configure ; make. You need to use gmake, BSD make probably won't work. Remember, run ./configure --help to see what build options are available. In order to compile Pidgin you need to have GTK+ 2.0 installed (as well as the development files!). The configure script will fail if you don't. If you don't have GTK+ 2.0 installed, you should install it using your distribution's package management tools. For sound support, you also need gstreamer 0.10 or higher. For spellchecking support, you need libgtkspell (http://gtkspell.sf.net/). Your distro of choice probably already includes these, just be sure to install the development packages. RUN === You should run 'make install' as root to make sure plugins and other files get installed into locations they want to be in. Once you've done that, you only need to run 'pidgin' or 'finch'. To get started, simply add a new account. If you come across a bug, please report it at: http://pidgin.im PLUGINS ======= If you do not wish to enable the plugin support within Purple, run the ./configure script with the --disable-plugins option and recompile your source code. This will prevent the ability to load plugins. 'make install' puts the plugins in $PREFIX/lib/purple (PREFIX being what you specified when you ./configure'd - it defaults to /usr/local). Purple looks for the plugins in that directory by default. Plugins can be installed per-user in ~/.purple/plugins as well. Pidgin and Finch also look in $PREFIX/lib/pidgin and $PREFIX/lib/finch for UI-specific, respectively. To build a plugin from a .c file, put it in the plugins/ directory in the source and run 'make filename.so', e.g. if you have the .c file 'kickass.c', put it in the plugins/ directory, and from that directory, run 'make kickass.so'.