head	1.36;
access;
symbols
	v0_69:1.35
	v0_68:1.35
	v0_67:1.35
	v0_65:1.35
	v0_64:1.34
	v0_63:1.34
	v0_62:1.34
	gaim_0_60:1.34
	v0_60:1.34
	ZERO_DOT_FUCKING_SIXTY:1.34
	v0_59_9:1.29
	v0_59_8:1.29
	gaim_0_59_7:1.29
	v0_60alpha3:1.33
	v0_59_6:1.29
	v0_59_5:1.29
	v0_59_4:1.29
	v0_59_3:1.29
	v0_59_2:1.29
	gtk1-stable:1.29.0.2
	v059:1.29
	v058:1.29
	v057:1.28
	v056:1.27
	v055:1.27
	v0_54:1.27;
locks; strict;
comment	@# @;


1.36
date	2003.09.28.17.33.54;	author chipx86;	state dead;
branches;
next	1.35;

1.35
date	2003.07.05.03.09.43;	author seanegan;	state Exp;
branches;
next	1.34;

1.34
date	2003.01.31.13.03.41;	author faceprint;	state Exp;
branches;
next	1.33;

1.33
date	2002.09.29.04.48.39;	author seanegan;	state Exp;
branches;
next	1.32;

1.32
date	2002.09.26.15.23.30;	author seanegan;	state Exp;
branches;
next	1.31;

1.31
date	2002.09.16.08.35.14;	author seanegan;	state Exp;
branches;
next	1.30;

1.30
date	2002.08.28.08.13.58;	author seanegan;	state Exp;
branches;
next	1.29;

1.29
date	2002.04.28.18.24.49;	author seanegan;	state Exp;
branches;
next	1.28;

1.28
date	2002.04.23.16.30.09;	author seanegan;	state Exp;
branches;
next	1.27;

1.27
date	2002.03.02.04.52.21;	author robflynn;	state Exp;
branches;
next	1.26;

1.26
date	2001.09.26.00.53.49;	author warmenhoven;	state Exp;
branches;
next	1.25;

1.25
date	2001.09.22.09.14.27;	author warmenhoven;	state Exp;
branches;
next	1.24;

1.24
date	2001.09.12.21.29.32;	author warmenhoven;	state Exp;
branches;
next	1.23;

1.23
date	2001.08.01.22.06.17;	author warmenhoven;	state Exp;
branches;
next	1.22;

1.22
date	2001.08.01.20.31.53;	author warmenhoven;	state Exp;
branches;
next	1.21;

1.21
date	2001.05.21.23.14.41;	author warmenhoven;	state Exp;
branches;
next	1.20;

1.20
date	2001.04.25.08.34.46;	author warmenhoven;	state Exp;
branches;
next	1.19;

1.19
date	2001.01.13.08.49.15;	author warmenhoven;	state Exp;
branches;
next	1.18;

1.18
date	2001.01.07.20.39.03;	author warmenhoven;	state Exp;
branches;
next	1.17;

1.17
date	2000.11.03.20.23.37;	author warmenhoven;	state Exp;
branches;
next	1.16;

1.16
date	2000.10.31.10.49.52;	author warmenhoven;	state Exp;
branches;
next	1.15;

1.15
date	2000.10.16.20.11.18;	author warmenhoven;	state Exp;
branches;
next	1.14;

1.14
date	2000.09.03.23.57.07;	author warmenhoven;	state Exp;
branches;
next	1.13;

1.13
date	2000.08.31.03.40.17;	author warmenhoven;	state Exp;
branches;
next	1.12;

1.12
date	2000.06.23.04.15.50;	author warmenhoven;	state Exp;
branches;
next	1.11;

1.11
date	2000.06.14.02.12.25;	author warmenhoven;	state Exp;
branches;
next	1.10;

1.10
date	2000.06.12.22.02.50;	author warmenhoven;	state Exp;
branches;
next	1.9;

1.9
date	2000.06.12.13.07.53;	author warmenhoven;	state Exp;
branches;
next	1.8;

1.8
date	2000.06.12.11.30.05;	author warmenhoven;	state Exp;
branches;
next	1.7;

1.7
date	2000.04.19.07.57.19;	author warmenhoven;	state Exp;
branches;
next	1.6;

1.6
date	2000.04.19.02.04.30;	author warmenhoven;	state Exp;
branches;
next	1.5;

1.5
date	2000.04.14.08.41.02;	author warmenhoven;	state Exp;
branches;
next	1.4;

1.4
date	2000.04.14.08.36.36;	author robflynn;	state Exp;
branches;
next	1.3;

1.3
date	2000.04.10.00.12.21;	author warmenhoven;	state Exp;
branches;
next	1.2;

1.2
date	2000.04.09.11.18.25;	author warmenhoven;	state Exp;
branches;
next	1.1;

1.1
date	2000.04.09.08.25.15;	author warmenhoven;	state Exp;
branches;
next	;


desc
@@


1.36
log
@Nuke SIGNALS.
@
text
@enum gaim_event {
	event_signon = 0,
	event_signoff,
	event_away,
	event_back,
	event_im_recv,
	event_im_send,
	event_buddy_signon,
	event_buddy_signoff,
	event_buddy_away,
	event_buddy_back,
	event_buddy_idle,
	event_buddy_unidle,
	event_blist_update,
	event_chat_invited,
	event_chat_join,
	event_chat_leave,
	event_chat_buddy_join,
	event_chat_buddy_leave,
	event_chat_recv,
	event_chat_send,
	event_warned,
	event_quit,
	event_new_conversation,
	event_set_info,
	event_draw_menu,
	event_im_displayed_sent,
	event_im_displayed_rcvd,
	event_chat_send_invite,
	event_got_typing,
	event_del_conversation,
	event_connecting,
	event_switch_conversation,
};

To add a signal handler, call the fuction gaim_signal_connect with the
following arguments:

void *, enum gaim_event, void *, void *

The first arg is the handle that was passed to gaim_plugin_init. You did
	save it, right?
The second arg is hopefully obvious.
The third arg is a pointer to a function that takes various args
	depending on which event you're dealing with.
The fourth arg is any data you want to send to your function, as a final
	argument.

To remove a signal handler, call the function gaim_signal_disconnect with the
following arguments:

void *, enum gaim_event, void *

The first arg is the handle that was passed to gaim_signal_init.
The second arg is hopefully obvious.
The third arg is a pointer to the function you attached.

Note that it deletes *all* functions matching the function you pass, not just
one. Sorry, that's just the way it works.

So here are the args that get passed to your functions in various events:

event_signon:
	struct gaim_connection *gc

	'gc' is the new connection.

event_signoff:
	struct gaim_connection *gc

	'gc' is the connection that is about to go offline. This is called before
	serv_close is, so you still have a chance to get one last message out.

event_away:
	struct gaim_connection *gc, char *state, char *message

	'gc' is the connection. Duh.
	'state' is confusing. We'll save that for now.
	'message' is the away message to be used.

	Each protocol sets up what away states it can have. These are all char *,
	and when the connection goes away it uses one of those. That's what state
	is.

	There's no way of telling from state and message whether you're actually
	away; it only gives state information, and a possible message.

	However, the protocols also are very nice (usually) and will set gc->away
	if they're in an away-like state (e.g. Away or N/A for ICQ, etc). You can
	use that for a more rigid (read "boolean") way of checking away-ness.

event_back:
	(none)

	This is deprecated and will not be called again. It will probably be
	removed eventually.

event_im_recv:
	struct gaim_connection *gc, char **who, char **text, guint32 *flags

	'gc' is the connection that received the message.
	'who' is the username of the person who sent the message.
	'text' is the actual strict text (with HTML tags and all) of the
		message they sent.
	'flags' is message flags.
	
	Note that you can modify these values. (You are encouraged to do so!)
	Note that *other* plugins can also modify these values, so you should
	check that they are not NULL, and try not to leave them as NULL.

	gc was placed as the first arg as opposed to the third for intuitiveness.
	Unfortunately, it means that most plugins that use this event need to be
	slightly modified and then recompiled.

	flags is actually a bit mask. AND with IM_FLAG_AWAY to see if they were
	away, etc.

event_im_send:
	struct gaim_connection *gc, char *who, char **text

	'gc' is the connection that you are about to send the message through.
	'who' is the username of the person you're sending the message to.
	'text' is the actual strict text (with HTML tags and all) of the
		message you're sending.

	Note that you can modify outgoing text. The **text points to a g_malloc'd
	data chunk that contains the text. If your plugin changes it, it should
	either not add length to the string, or g_free *text and g_malloc a new
	segment. Since plugins can modify this, you should not try and remember it
	in your plugin.

event_buddy_signon:
	struct gaim_connection *gc, char *who
	
	'who' is who signed on. (There is currently no way to see which connection
	reported that the buddy came online. Hopefully this will happen soon.)

event_buddy_signoff:
	struct gaim_connection *gc, char *who

	'who' is who signed off.

event_buddy_away:
	struct gaim_connection *gc, char *who

	'who' is who went away.

event_buddy_back:
	struct gaim_connection *gc, char *who

	'who' is who is no longer away.

event_buddy_idle:
	struct gaim_connection *gc, char *who

	'who' is who went idle.

event_buddy_unidle:
	struct gaim_connection *gc, char *who

	'who' is who is no longer idle.

event_blist_update:
	(none)

	called when the idle times are updated in the buddy list

event_chat_invited:
	struct gaim_connection *gc, char *who, char *room, char *message

	'gc' is the connection that received the invitation.
	'who' is who invited you to a chat room.
	'room' is the room they invited you to.
	'message' is the (optional) message they sent to invite you, and may be
	an empty string.

event_chat_join:
	struct gaim_connection *gc, int id, char *room

	'gc' is the connection that joined the room.
	'id' is the id of the room. See, each room is given an id unique
	within the connection. The struct conversation*'s in gc->buddy_chats
	have an 'id' field that's only used if it's is_chat member is TRUE.
	'id' is the *only* way to detect which chat room you actually mean,
	because the name of the chat room is not always unique (for example,
	MSN always uses "MSN Chat" as its name, since group chats in MSN
	don't actually have names).
	'room' is the chat room that you have just joined.

event_chat_leave:
	struct gaim_connection *gc, int

	'gc' is the connection that joined the room.
	'id' is the id of the chat room that you have just left.

event_chat_buddy_join:
	struct gaim_connection *gc, int id, char *who

	'gc' is the connection that the chat room is attached to.
	'id' is the id of the room the person joined.
	'who' is the screenname of the person who joined.

	This is also triggered upon entering the room for every person in the
	room, including yourself. (E.g. if you join a room that already had 3
	people in it this will be called 4 times, once for each of them and
	once again for you. You will not always be the last one this is called
	for though.)

event_chat_buddy_leave:
	struct gaim_connection *gc, int id, char *who

	'gc' is the connection that the chat room is attached to.
	'id' is the id of the room the person left.
	'who' is the screenname of the person who left.

event_chat_recv:
	struct gaim_connection *gc, int id, char **who, char **text

	'gc' is the connection that received the message.
	'who' should be too.
	'text' is the message that got sent.
	'id' is the id of the room that received the message (see
	event_chat_join)

	Like event_im_recv, you are allowed and encouraged to change
	these values	

	Note that because of the bizarre way chat works, you also receive
	messages that you send. I didn't design it, AOL did.

event_chat_send:
	struct gaim_connection *gc, int id, char **text

	'gc' is the connection that the message is about to be sent on.
	'id' is the id of the room to which you're sending the message.
	'text' is what you're about to say, linkified/HTML-ized, but not
	TOC-escaped.

	Be aware that you receive messages you send (as noted above). This
	event will be called before you actually send the message though.
	The **text pointer behaves the same as the **text pointer for the
	event_im_send event above; so read the note about it there.

event_warned:
	struct gaim_connection *gc, char *who, int level

	'gc' is the account that got warned.
	'who' is who warned you. Note that this can be NULL, indicating either
	an anonymous warning, or your warning level has dropped.
	'level' is your new warning level.

event_quit:
	(none)

	Called when gaim quits normally.  This can be called from either the
	signed on state or the signed off state (from either the Cancel button
	in the login window or the Quit option in the File menu on the buddy
	list). If gaim dies or is murdered, this won't be called. It's not my
	fault, it's Seg's.

event_new_conversation:
	char *who

	'who' is who the conversation is with. This gets called when a new
	conversation window is created. You can use find_conversation(char *)
	to then find the struct conversation * and modify those values.

event_set_info:
        struct gaim_connection *gc, char *info

        Called when the user sends his profile to the server.  'info' is the
        profile being sent. 

event_draw_menu:
	GtkWidget *menu, char *name

	Called when you right-click on a buddy.

	'menu' is the menu that is about to be displayed.
	'name' is the name of the buddy that was clicked.

event_im_displayed_sent:
	struct gaim_connection *gc, char *who, char **what

	This is called after what you send is displayed but before it's
	actually sent. That is, when the user clicks the "send" button
	in an IM window, first it gets passed to event_im_send handlers,
	then it gets displayed, then it gets passed to these handlers, and
	then it gets sent over the wire. This is useful for when you want
	to encrypt something on the way out.

	'gc' is the connection the message is sent on.
	'who' is who the message is for.
	'what' is what was sent. It's expected that you modify this. If
	you set *what to NULL the message won't be sent, but the preferred
	way of doing this is to attach to event_im_send so that it really
	won't be displayed at all.

event_im_displayed_rcvd:
	struct gaim_connection *gc, char *who, char *what, guint32 flags, time_t time

	This is called after what you receive is displayed. This is useful
	for displaying an autoresponse after the message that triggered it.
	There are a bunch of things that are odd about this, especially
	when dealing with being away, so be careful.

	'gc' is the connection the message was received on.
	'who' is who sent the message.
	'what' is what was sent.
	'flags' is flags on the message.
	'time' is the time the message was received--it may be very different from the
	 time this signal gets called

event_chat_send_invite:
	struct gaim_connection *gc, int id, char *who, char **msg

	This is called just before you're about to invite someone. It's
	useful for if you want to pass someone a key so that they can
	participate in a group encrypted chat (ahem).

	'gc' is the connection the invite is sent on.
	'id' is the id of the room you're inviting them to.
	'who' is who you're inviting.
	'msg' is the message they'll receive when they're invited. It may be
	NULL. Setting this to NULL won't stop the invitation from going thru.

event_got_typing:
	struct gaim_connection *gc, char *who

	This is called when a buddy starts typing you and is called 
	differently depending on the protocol.  MSN requires that a 
	conversation is already in progress, and may send more than
	one notification while typing.  OSCAR can receive typing 
	notifications in direct IMs, and Yahoo can receive them any
	time.

	'gc' 	is the connection the typing is sent to.
	'who' 	is the person typing to you.

event_del_conversation:
	struct conversation *c

	This is called when a conversation window is closed.  It is
	called before any memory is deallocated so you are able to
	access any data related to the conversation without breaking
	anything.

	'c'	is the conversation being closed.

event_connecting:
	struct gaim_account *u

	This is called when Gaim attempts to bring a user on-line. The
	boolean u->connecting is set to true, and connecting_count
	incremented. The attempt can end with event_signon or event_signoff
	being called, depending upon whether the attempt was a sucess or
	a failure. In both cases, u->connecting is set to false and the
	counter decremented.

	'u'	is the account being connected.

event_conversation_switch:
	GaimConversation *c

	This is called when a new conversation has become the active conversation
	in its GaimWindow.

	Using this in conjuction with GTK's focus-in-event will allow you to trigger
	callbacks anytime a conversation receives focus.

	'c' 	is the conversation that has just received focus.
@


1.35
log
@Yeah, this *should* work.  But maybe it won't.  I sure as hell ain't testin it.
That's what we pay you for you.  This is a plugin event that gets triggered when
the user switches tabs in a window.  Used in conjunction with GTK signals, you
should be able to get a good idea of when a conversation has taken focus.

Maybe now the notify plugin can be fixed.

While doing this, I noticed that a lot of the plugin documentation stuff is
woefully outdated.  Someone who wants to get involved with a non-coding project
is welcome to send a patch.
@
text
@@


1.34
log
@aim_user is dead.  long live gaim_account.
@
text
@d33 1
d361 11
@


1.33
log
@You win, McQueen.
@
text
@d350 1
a350 1
	struct aim_user *u
@


1.32
log
@A long annoying patch by one Robert McQueen.
@
text
@d347 2
a348 2
	'c'	is he conversation being closed.
	
d358 1
a358 1
	
@


1.31
log
@Rob McQueen added a mute feature to his nice little docklet.  I added a
queuing feature.  Configure the docklet in the plugins dialog to queue
unread messages, and when you receive a message the docklet will eat it up
and show a little message pending icon.  Click on it, and read your message.

ICQ people will like it.

I also made plugin_event use a va_list.

I bet this breaks perl.
@
text
@d349 1
a349 1
event_connecting
d353 1
a353 1
	boolean u->connecting is set to true, and a global counter
d359 1
a359 1
	'u'	is the account being connected
@


1.30
log
@obobo
@
text
@d32 1
d299 1
a299 1
	struct gaim_connection *gc, char *who, char *what, guint32 flags
d310 2
d338 1
d348 12
@


1.29
log
@typos
@
text
@d31 1
d335 9
@


1.28
log
@event_chat_recv takes char** arguments, so you can change the incoming text
and sender.

event_im_recv takes a guint32* for its flags, so you can change the flags too.
@
text
@d38 1
a38 1
The first arg is the handle that was passed to gaim_signal_init. You did
@


1.27
log
@0.53 :)
@
text
@d96 1
a96 1
	struct gaim_connection *gc, char **who, char **text, guint32 flags
d214 1
a214 1
	struct gaim_connection *gc, int id, char *who, char *text
d221 3
@


1.26
log
@hi usa
@
text
@d29 2
a30 1
	event_chat_send_invite
d318 13
@


1.25
log
@you say potato, i say potato
you say tomato, i say tomato
potato, potato
tomato, tomato
let's call the whole thing off.

*sigh*. it just doesn't work as well when it's typed. but you wouldn't want to hear me sing it.
@
text
@d306 1
a306 1
	struct gaim_connection *gc, int id, char *who, char *msg
d315 2
a316 1
	'msg' is the message they'll receive when they're invited.
@


1.24
log
@One of the girls on the floor of my sister's dorm lost both her parents when their plane was hijacked and crashed into the World Trade Center. my girlfriend's boss's sister-in-law's brother died when the building collapsed. my parents flew to atlanta on monday; they're safe but currently stranded there. they had planned on flying to Raleigh, NC today but now are just hoping to be able to fly home soon. how did this happen?
@
text
@a22 1
	event_error,
d28 2
a29 1
	event_im_displayed_rcvd
d174 1
a174 1
	struct gaim_connection *gc, char *room
d177 7
d187 1
a187 1
	struct gaim_connection *gc, char *room
d190 1
a190 1
	'room' is the chat room that you have just left.
d193 1
a193 1
	struct gaim_connection *gc, char *room, char *who
d196 1
a196 1
	'room' is the room the person joined.
d206 1
a206 1
	struct gaim_connection *gc, char *room, char *who
d209 1
a209 1
	'room' is the room the person left.
d213 1
a213 1
	struct gaim_connection *gc, char *room, char *who, char *text
a215 1
	'room' should be obvious by now.
d218 2
d225 1
a225 1
	struct gaim_connection *gc, char *room, char **text
d228 1
a228 1
	'room'. Need I say more.
a244 9
event_error:
	int error

	'error' is the number of the error as defined by the TOC PROTOCOL
	document, which can be found in the docs/ directory of the source
	tree. Note that if the person is using Oscar, this number is often
	plain wrong, and this event may not always be triggered on error.
	Experiment to find what is reliable.

d304 12
@


1.23
log
@heh. i confused myself.
@
text
@d95 1
a95 1
	struct gaim_connection *gc, char **who, char **text
d101 1
d111 3
d294 1
a294 1
	struct gaim_connection *gc, char *who, char *what
d304 1
@


1.22
log
@I haven't actually tested that it works, but theoretically it does.
@
text
@d28 2
a29 1
	event_im_displayed
d272 1
a272 1
event_im_displayed:
d280 1
a280 2
	to encrypt something on the way out, or when you want to send a
	response and have it displayed after what triggered the response.
d282 2
a283 2
	'gc' is the connection the message was received on.
	'who' is who sent the message.
d288 12
@


1.21
log
@la la la la la la. cleanups. and proxy for napster.
@
text
@d26 3
a28 1
	event_set_info
d262 26
@


1.20
log
@patch from sean egan for event_set_info. why this would be necessary... i guess we'll see :)
@
text
@d223 1
a223 1
	char *who, int level
d225 1
@


1.19
log
@argh
@
text
@d25 2
a26 1
	event_new_conversation
d253 6
@


1.18
log
@erg
@
text
@d67 12
a78 1
	(none)
d80 3
a82 3
	This is fucked up for now. Currently all connections are told to use the
	same away message when the user wants to be Away. The away message that
	is used can be obtained from global variables.
d86 3
@


1.17
log
@idle times for single connections; deleting an account signs it off if need be
@
text
@d100 5
a104 2
	Note that you can modify outgoing text. (You are _not_ encouraged to
		do so ;-) .)
d204 2
@


1.16
log
@i have homework i need to be doing. it's due in less than 7 hours, and i haven't started and i need to sleep.
@
text
@d14 1
d133 5
@


1.15
log
@Plugins work again, I think. There may still be some bugginess.
@
text
@a13 1
	event_blist_update,
d103 1
a103 1
	char *who
d109 1
a109 1
	char *who
d114 1
a114 1
	char *who
d119 1
a119 1
	char *who
d124 1
a124 1
	char *who
d129 1
a129 1
	char *who
a131 6

event_blist_update:
	(none)
	
	This event is called when the buddylist is updated (automatically every
	20 seconds for every connection, though the updates are usually syncopated)
@


1.14
log
@better at informing the user of error now
@
text
@d12 2
d56 1
a56 1
	(none)
d58 1
a58 2
	Note that you can get the username (which would probably be the only
	useful information here) from other places. (Read gaim.h for details.)
d61 4
a64 1
	(none)
d69 3
a71 2
	Note that the away message that's being used can be retrieved from a
	global variable. (Read gaim.h for details.)
d77 1
a77 1
	char **who, char **text
d79 1
d88 4
d93 1
a93 1
	char *who, char **text
d95 1
d106 2
a107 1
	'who' is who signed on.
d124 10
d138 1
a138 1
	20 seconds)
d141 1
a141 1
	char *who, char *room, char *message
d143 1
d150 1
a150 1
	char *room
d152 1
d156 1
a156 1
	char *room
d158 1
d162 1
a162 1
	char *room, char *who
d164 1
d175 1
a175 1
	char *room, char *who
d177 1
d182 1
a182 1
	char *room, char *who, char *text
d184 1
d193 1
a193 1
	char *room, char **text
d195 1
@


1.13
log
@event_new_conversation
@
text
@d186 3
a188 3
	tree. Note that if the person is using Oscar, this number can often
	be misleading, as not all the errors have been worked out, and some
	do not translate to TOC error codes cleanly.
@


1.12
log
@More mods to how plugins work.
@
text
@d22 2
a23 1
	event_quit
d198 7
@


1.11
log
@It's a good thing I proofread things; otherwise, there would be a lot of
confused people when 0.9.20 comes out.
@
text
@d195 2
a196 3
	list). Note that for the applet, this will never be called. If gaim
	dies or is murdered, this won't be called. It's not my fault, it's
	Seg's.
@


1.10
log
@Heh, whoops. you can send messages to offline people now.
@
text
@d141 6
@


1.9
log
@More updates to plugins
@
text
@d164 3
@


1.8
log
@Plugins got updated.
@
text
@d183 6
a188 2
	Called when gaim quits normally. If gaim dies or is killed, this won't
	be called. It's not my fault, it's Seg's.
@


1.7
log
@Added event_back and event_buddy_back events.
@
text
@d12 11
a22 1
	event_blist_update
d116 69
@


1.6
log
@Let's see if I can remember everything I did:

	- Fixed a bug I let slip. If you choose the new option to not play
	  login sounds when you log in, and then quit before the timeout is
	  up, it would save that you didn't want login sounds at all.

	- Added two new plugin events: event_away and event_buddy_away.

	- Made GtkWidget *imaway in away.c and void play(uchar *, int) in
	  sound.c not static any more (though not referenced in gaim.h).
	  This is so plugins can use those (and not have to worry about
	  writing their own sound code).

	- Wrote a quick plugin to auto-iconify windows when you go away. I
	  had just been locally patching my own copy, since I figured it wasn't
	  worth including as an option. It also demonstrates some of the issues
	  of deciding between USE_APPLET and not. Perhaps plugins are the way
	  to go with some things that would otherwise have been options (for
	  example, the Lag-O-Meter is one of those things that could possibly
	  have been a plugin instead of hard-coded in).

I think that's everything.
@
text
@d5 1
d11 1
d46 1
a46 1
	useful information here) from other places. (Read gaim.h for details).
d54 6
d95 5
@


1.5
log
@I'm so anal sometimes :P
@
text
@d4 1
d9 1
d49 3
d82 5
@


1.4
log
@Hmm
@
text
@d81 2
a82 2
	This event is called when the buddylist is updated (automatically every 20 seconds)
	
@


1.3
log
@Added a spell check plugin. Shows proof-of-concept, mostly.
@
text
@d8 1
d77 6
@


1.2
log
@Woohoo, the landing of the plugins. Nearly everything necessary is here. The
only thing missing is that you can't load a plugin without signing on first
(at least, not without some trickery).
@
text
@d58 1
a58 1
	char **who, char **text
d64 1
a64 1
	Note that you can modify these values. (You are _not_ encouraged to
@


1.1
log
@Notes on how to do plugins with gaim (note that this hasn't been
implemented completely yet, this is just how it *should* work).
@
text
@d13 1
a13 1
enum gaim_event, void *, void *
d15 4
a18 2
The first arg is hopefully obvious.
The second arg is a pointer to a function that takes various args
d20 1
a20 1
The third arg is any data you want to send to your function, as a final
d23 12
d38 1
a38 1
	char *name
d40 2
a41 2
	'name' is your username. (Note that this can be returned through
		other methods.)
d54 2
@

