Mercurial > pidgin
comparison doc/TCL-HOWTO.dox @ 25925:6e1967b0f90b
Change "screen name" to "username" or "buddy name" in a whole bunch of
places in the code. I've been using the definitions from the jabber
specs, where "user" is me and "buddy" is someone on my buddy list.
author | Mark Doliner <mark@kingant.net> |
---|---|
date | Mon, 26 Jan 2009 09:12:04 +0000 |
parents | 73e827a93ae9 |
children | e5ebf3abd9f8 |
comparison
equal
deleted
inserted
replaced
25924:584063555949 | 25925:6e1967b0f90b |
---|---|
330 intended to be a list only of their arguments. Signal callbacks will | 330 intended to be a list only of their arguments. Signal callbacks will |
331 be made in their own namespace, and arguments to those signal | 331 be made in their own namespace, and arguments to those signal |
332 callbacks will live in the namespace @c event underneath that | 332 callbacks will live in the namespace @c event underneath that |
333 namespace. To briefly illustrate, the signal @c receiving-im-msg is | 333 namespace. To briefly illustrate, the signal @c receiving-im-msg is |
334 provided with three arguments; the account on which the IM was | 334 provided with three arguments; the account on which the IM was |
335 received, the screen name of the user sending the IM, and the text of | 335 received, the name of the buddy sending the IM, and the text of |
336 the IM. These arguments live in the variables @c event::account, | 336 the IM. These arguments live in the variables @c event::account, |
337 @c event::sender, and @c event::buffer, respectively. Therefore a callback | 337 @c event::sender, and @c event::buffer, respectively. Therefore a callback |
338 which notifies the user of an incoming IM containing the word 'shizzle' | 338 which notifies the user of an incoming IM containing the word 'shizzle' |
339 might look like this: | 339 might look like this: |
340 | 340 |