Mercurial > pidgin
comparison README @ 20407:1122d47583a1
explicit merge of 'd42ad2da81f881b2fbd2fb080cc70a843bc70d02'
and '8582c561c020d2d1e8d358e2e7cd9e3da113ed9e'
to branch 'im.pidgin.cpw.khc.msnp14'
author | Ka-Hing Cheung <khc@hxbc.us> |
---|---|
date | Wed, 02 May 2007 05:25:27 +0000 |
parents | 83ec0b408926 |
children | 3bd360f26a9e |
comparison
equal
deleted
inserted
replaced
20406:7acc792487f2 | 20407:1122d47583a1 |
---|---|
39 | 39 |
40 You should run 'make install' as root to make sure plugins and other files | 40 You should run 'make install' as root to make sure plugins and other files |
41 get installed into locations they want to be in. Once you've done that, | 41 get installed into locations they want to be in. Once you've done that, |
42 you only need to run 'pidgin' or 'finch'. | 42 you only need to run 'pidgin' or 'finch'. |
43 | 43 |
44 Protocol plugins (PRPLs) are now automatically loaded. Simply go to the | 44 To get started, simply add a new account. |
45 account editor, add a new account, and all supported protocols will be | |
46 there. Be sure to use OSCAR (AIM/ICQ) and not the old TOC or ICQ plugins. | |
47 | 45 |
48 Read below for protocol-specific information. | 46 If you come across a bug, please report it at: http://pidgin.im |
49 | |
50 | 47 |
51 PLUGINS | 48 PLUGINS |
52 ======= | 49 ======= |
53 | 50 |
54 If you do not wish to enable the plugin support within Purple, run the | 51 If you do not wish to enable the plugin support within Purple, run the |
55 ./configure script with the --disable-plugins option and recompile your | 52 ./configure script with the --disable-plugins option and recompile your |
56 source code. This will prevent the ability to load plugins. | 53 source code. This will prevent the ability to load plugins. |
57 | 54 |
58 'make install' puts the plugins in $PREFIX/lib/purple (PREFIX being what | 55 'make install' puts the plugins in $PREFIX/lib/purple (PREFIX being what |
59 you specified when you ./configure'd - it defaults to /usr/local). Purple | 56 you specified when you ./configure'd - it defaults to /usr/local). Purple |
60 looks for the plugins in that directory by default, but they do not have | 57 looks for the plugins in that directory by default. Plugins can be installed |
61 to be there to use them. Also, plugins have a .so extension by default, | 58 per-user in ~/.purple/plugins as well. Pidgin and Finch also look in |
62 though they do not have to. | 59 $PREFIX/lib/pidgin and $PREFIX/lib/finch for UI-specific, respectively. |
63 | 60 |
64 To build a plugin from a .c file, put it in the plugins/ directory in | 61 To build a plugin from a .c file, put it in the plugins/ directory in |
65 the source and run 'make filename.so', e.g. if you have the .c file | 62 the source and run 'make filename.so', e.g. if you have the .c file |
66 'kickass.c', put it in the plugins/ directory, and from that directory, | 63 'kickass.c', put it in the plugins/ directory, and from that directory, |
67 run 'make kickass.so'. | 64 run 'make kickass.so'. |
68 | 65 |
69 | |
70 NOTES | |
71 ===== | |
72 | |
73 If you manually set a command for your browser or sound player options, | |
74 make sure to put double-quotes around the "%s", otherwise bad things may | |
75 happen. | |
76 | |
77 If you come across a bug, please report it to http://pidgin.im/. | |
78 | |
79 | |
80 PROTOCOL INFORMATION | |
81 ==================== | |
82 | |
83 Each protocol is hacked by both Rob and Eric, though there is one person | |
84 that kind of "owns" a protocol (mostly indicating that they were the | |
85 person that originally wrote it). Their name will be next to the protocol; | |
86 they're the people to complain to when something doesn't work ;). | |
87 | |
88 | |
89 TOC (Mark) | |
90 === | |
91 | |
92 You shouldn't use TOC, you should use Oscar instead. TOC can sync your | |
93 buddy list with the server (if it's not too long), and can respond to file | |
94 transfer requests (both sending and receiving). Other than that, there's | |
95 nothing it can do that Oscar can't, yet. The TOC protocol doesn't allow | |
96 retrieval of away messages; isn't capable of sending or receiving buddy | |
97 icons; it also can't make file transfer requests. | |
98 | |
99 | |
100 Oscar (Mark) | |
101 ===== | |
102 | |
103 Oscar is the default protocol. It is recommended that you use Oscar for | |
104 both AIM and ICQ, as TOC isn't very featureful and the old ICQ protocol no | |
105 longer works. | |
106 | |
107 For AIM, Oscar can get people's away messages. It can request and accept | |
108 Direct Connections, and has limited support for file transfer. IM Image | |
109 does not currently work. It can send and receive buddy icons if you have | |
110 GdkPixbuf. | |
111 | |
112 For ICQ, it supports nearly everything that the old ICQ plugin supported, | |
113 which isn't much. To use Oscar for ICQ, enter your ICQ UIN as the | |
114 screenname. The default host/port will work. You'll need to use a different | |
115 client to register a new ICQ account if you don't have one yet. | |
116 | |
117 | |
118 Yahoo (Sean) | |
119 ===== | |
120 | |
121 Yahoo is currently using the new YMSG protocol that newer official Yahoo | |
122 clients are using. This protocol is much better than the old one, and | |
123 tends to be somewhat more reliable. However, the Yahoo service is still | |
124 flaky at best. | |
125 | |
126 | |
127 IRC (Ethan) | |
128 === | |
129 | |
130 There are three ways to join an IRC chat room. The first is the File->Join | |
131 A Chat menu option in the Buddy List window. The second is the "Chat" | |
132 button at the bottom of the buddy list. The third is to type "/join #name" | |
133 in an IM window where the "Send Message As" menu is set to your IRC | |
134 account. There are other / commands that work in IM and Chat windows for | |
135 IRC, /help will give you a list of them. | |
136 | |
137 | |
138 MSN | |
139 === | |
140 | |
141 With MSN you can join a conversation with several people, but you can't | |
142 invite people from the IM window yet. | |
143 | |
144 | |
145 Jabber (Nathan) | |
146 ====== | |
147 | |
148 Transports aren't currently supported at all, though if you have a | |
149 transport already subscribed Purple will use it (you can't add or remove | |
150 transports though). In order to use a server other than jabber.org, set | |
151 your username to include the server, e.g. warmenhoven@mycompany.com. This | |
152 is the actual format of the Jabber ID anyway; Jabber is email with online | |
153 notification. You can register a new Jabber account by checking the | |
154 appropriate box in the account editor for your Jabber account. | |
155 | |
156 | |
157 Zephyr (Sean) | |
158 ====== | |
159 | |
160 Let me start off by saying how much I really despise Zephyr. They do a | |
161 lot of things that make me realize why this never caught on. For those | |
162 of you who are unfortunate enough to feel compelling need to use this, | |
163 Purple now has a Zephyr plugin. It can currently sign on/off, handles | |
164 presence/buddy lists (it even imports your .anyone file!), and can | |
165 send/receive personal messages. A lot of stuff is missing, this is just | |
166 a real rough first stab at it. | |
167 | |
168 | |
169 Gadu-Gadu (Sean) | |
170 ========= | |
171 | |
172 I really shouldn't be taking credit for Gadu-Gadu, I'm just the person who | |
173 commits the patches that Arkadiusz Miskiewicz gives me. Gadu-Gadu is an IM | |
174 system most similar to ICQ that is quite popular in Poland. It can manage | |
175 your server-side buddy list through the Protocol Actions menu. You'll need | |
176 to use a different client to register a new account if you don't have one | |
177 yet. |