source: protocols/nogaim.h @ a72af0d

Last change on this file since a72af0d was 0ebf919, checked in by Wilmer van der Gaast <wilmer@…>, at 2010-08-21T22:25:37Z

Pass "user is mobile" info coming from OSCAR up to BitlBee and show mobile
people as away=Mobile. Bug #462 (and others for other protocols).
  • Property mode set to 100644
File size: 13.2 KB
Line 
1  /********************************************************************\
2  * BitlBee -- An IRC to other IM-networks gateway                     *
3  *                                                                    *
4  * Copyright 2002-2010 Wilmer van der Gaast and others                *
5  \********************************************************************/
6
7/*
8 * nogaim, soon to be known as im_api. Not a separate product (unless
9 * someone would be interested in such a thing), just a new name.
10 *
11 * Gaim without gaim - for BitlBee
12 *
13 * This file contains functions called by the Gaim IM-modules. It contains
14 * some struct and type definitions from Gaim.
15 *
16 * Copyright (C) 1998-1999, Mark Spencer <markster@marko.net>
17 *                          (and possibly other members of the Gaim team)
18 * Copyright 2002-2007 Wilmer van der Gaast <wilmer@gaast.net>
19 */
20
21/*
22  This program is free software; you can redistribute it and/or modify
23  it under the terms of the GNU General Public License as published by
24  the Free Software Foundation; either version 2 of the License, or
25  (at your option) any later version.
26
27  This program is distributed in the hope that it will be useful,
28  but WITHOUT ANY WARRANTY; without even the implied warranty of
29  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
30  GNU General Public License for more details.
31
32  You should have received a copy of the GNU General Public License with
33  the Debian GNU/Linux distribution in /usr/share/common-licenses/GPL;
34  if not, write to the Free Software Foundation, Inc., 59 Temple Place,
35  Suite 330, Boston, MA  02111-1307  USA
36*/
37
38#ifndef _NOGAIM_H
39#define _NOGAIM_H
40
41#if(__sun)
42#include <inttypes.h>
43#else
44#include <stdint.h>
45#endif
46
47#include "lib/events.h"
48
49#include "bitlbee.h"
50#include "account.h"
51#include "proxy.h"
52#include "query.h"
53#include "md5.h"
54#include "ft.h"
55
56#define BUDDY_ALIAS_MAXLEN 388   /* because MSN names can be 387 characters */
57
58#define WEBSITE "http://www.bitlbee.org/"
59
60/* Sharing flags between all kinds of things. I just hope I won't hit any
61   limits before 32-bit machines become extinct. ;-) */
62#define OPT_LOGGED_IN   0x00000001
63#define OPT_LOGGING_OUT 0x00000002
64#define OPT_AWAY        0x00000004
65#define OPT_MOBILE      0x00000008
66#define OPT_DOES_HTML   0x00000010
67#define OPT_LOCALBUDDY  0x00000020 /* For nicks local to one groupchat */
68#define OPT_TYPING      0x00000100 /* Some pieces of code make assumptions */
69#define OPT_THINKING    0x00000200 /* about these values... Stupid me! */
70
71/* ok. now the fun begins. first we create a connection structure */
72struct im_connection
73{
74        account_t *acc;
75        uint32_t flags;
76       
77        /* each connection then can have its own protocol-specific data */
78        void *proto_data;
79       
80        /* all connections need an input watcher */
81        int inpa;
82        guint keepalive;
83       
84        /* buddy list stuff. there is still a global groups for the buddy list, but
85         * we need to maintain our own set of buddies, and our own permit/deny lists */
86        GSList *permit;
87        GSList *deny;
88        int permdeny;
89       
90        char displayname[128];
91        char *away;
92       
93        int evil;
94       
95        /* BitlBee */
96        bee_t *bee;
97       
98        GSList *groupchats;
99};
100
101struct groupchat {
102        struct im_connection *ic;
103
104        /* stuff used just for chat */
105        /* The in_room variable is a list of handles (not nicks!), kind of
106         * "nick list". This is how you can check who is in the group chat
107         * already, for example to avoid adding somebody two times. */
108        GList *in_room;
109        //GList *ignored;
110       
111        //struct groupchat *next;
112        /* The title variable contains the ID you gave when you created the
113         * chat using imcb_chat_new(). */
114        char *title;
115        /* Use imcb_chat_topic() to change this variable otherwise the user
116         * won't notice the topic change. */
117        char *topic;
118        char joined;
119        /* This is for you, you can add your own structure here to extend this
120         * structure for your protocol's needs. */
121        void *data;
122        void *ui_data;
123};
124
125struct buddy {
126        char name[80];
127        char show[BUDDY_ALIAS_MAXLEN];
128        int present;
129        int evil;
130        time_t signon;
131        time_t idle;
132        int uc;
133        guint caps; /* woohoo! */
134        void *proto_data; /* what a hack */
135        struct im_connection *ic; /* the connection it belongs to */
136};
137
138struct prpl {
139        int options;
140        /* You should set this to the name of your protocol.
141         * - The user sees this name ie. when imcb_log() is used. */
142        const char *name;
143        void *data;
144
145        /* Added this one to be able to add per-account settings, don't think
146         * it should be used for anything else. You are supposed to use the
147         * set_add() function to add new settings. */
148        void (* init)           (account_t *);
149        /* The typical usage of the login() function:
150         * - Create an im_connection using imcb_new() from the account_t parameter.
151         * - Initialize your myproto_data struct - you should store all your protocol-specific data there.
152         * - Save your custom structure to im_connection->proto_data.
153         * - Use proxy_connect() to connect to the server.
154         */
155        void (* login)          (account_t *);
156        /* Implementing this function is optional. */
157        void (* keepalive)      (struct im_connection *);
158        /* In this function you should:
159         * - Tell the server about you are logging out.
160         * - g_free() your myproto_data struct as BitlBee does not know how to
161         *   properly do so.
162         */
163        void (* logout)         (struct im_connection *);
164       
165        /* This function is called when the user wants to send a message to a handle.
166         * - 'to' is a handle, not a nick
167         * - 'flags' may be ignored
168         */
169        int  (* buddy_msg)      (struct im_connection *, char *to, char *message, int flags);
170        /* This function is called then the user uses the /away IRC command.
171         * - 'state' contains the away reason.
172         * - 'message' may be ignored if your protocol does not support it.
173         */
174        void (* set_away)       (struct im_connection *, char *state, char *message);
175        /* Implementing this function is optional. */
176        void (* get_away)       (struct im_connection *, char *who);
177        /* Implementing this function is optional. */
178        int  (* send_typing)    (struct im_connection *, char *who, int flags);
179       
180        /* 'name' is a handle to add/remove. For now BitlBee doesn't really
181         * handle groups, just set it to NULL, so you can ignore that
182         * parameter. */
183        void (* add_buddy)      (struct im_connection *, char *name, char *group);
184        void (* remove_buddy)   (struct im_connection *, char *name, char *group);
185       
186        /* Block list stuff. Implementing these are optional. */
187        void (* add_permit)     (struct im_connection *, char *who);
188        void (* add_deny)       (struct im_connection *, char *who);
189        void (* rem_permit)     (struct im_connection *, char *who);
190        void (* rem_deny)       (struct im_connection *, char *who);
191        /* Doesn't actually have UI hooks. */
192        void (* set_permit_deny)(struct im_connection *);
193       
194        /* Request profile info. Free-formatted stuff, the IM module gives back
195           this info via imcb_log(). Implementing these are optional. */
196        void (* get_info)       (struct im_connection *, char *who);
197        void (* set_my_name)    (struct im_connection *, char *name);
198        void (* set_name)       (struct im_connection *, char *who, char *name);
199       
200        /* Group chat stuff. */
201        /* This is called when the user uses the /invite IRC command.
202         * - 'who' may be ignored
203         * - 'message' is a handle to invite
204         */
205        void (* chat_invite)    (struct groupchat *, char *who, char *message);
206        /* This is called when the user uses the /part IRC command in a group
207         * chat. You just should tell the user about it, nothing more. */
208        void (* chat_leave)     (struct groupchat *);
209        /* This is called when the user sends a message to the groupchat.
210         * 'flags' may be ignored. */
211        void (* chat_msg)       (struct groupchat *, char *message, int flags);
212        /* This is called when the user uses the /join #nick IRC command.
213         * - 'who' is the handle of the nick
214         */
215        struct groupchat *
216             (* chat_with)      (struct im_connection *, char *who);
217        /* This is used when the user uses the /join #channel IRC command.  If
218         * your protocol does not support publicly named group chats, then do
219         * not implement this. */
220        struct groupchat *
221             (* chat_join)      (struct im_connection *, const char *room,
222                                 const char *nick, const char *password, set_t **sets);
223        /* Change the topic, if supported. Note that BitlBee expects the IM
224           server to confirm the topic change with a regular topic change
225           event. If it doesn't do that, you have to fake it to make it
226           visible to the user. */
227        void (* chat_topic)     (struct groupchat *, char *topic);
228       
229        /* If your protocol module needs any special info for joining chatrooms
230           other than a roomname + nickname, add them here. */
231        void (* chat_add_settings)      (account_t *acc, set_t **head);
232        void (* chat_free_settings)     (account_t *acc, set_t **head);
233       
234        /* You can tell what away states your protocol supports, so that
235         * BitlBee will try to map the IRC away reasons to them. If your
236         * protocol doesn't have any, just return one generic "Away". */
237        GList *(* away_states)(struct im_connection *ic);
238       
239        /* Mainly for AOL, since they think "Bung hole" == "Bu ngho le". *sigh*
240         * - Most protocols will just want to set this to g_strcasecmp().*/
241        int (* handle_cmp) (const char *who1, const char *who2);
242
243        /* Implement these callbacks if you want to use imcb_ask_auth() */
244        void (* auth_allow)     (struct im_connection *, const char *who);
245        void (* auth_deny)      (struct im_connection *, const char *who);
246
247        /* Incoming transfer request */
248        void (* transfer_request) (struct im_connection *, file_transfer_t *ft, char *handle );
249       
250        void (* buddy_data_add) (struct bee_user *bu);
251        void (* buddy_data_free) (struct bee_user *bu);
252       
253        /* Some placeholders so eventually older plugins may cooperate with newer BitlBees. */
254        void *resv1;
255        void *resv2;
256        void *resv3;
257        void *resv4;
258        void *resv5;
259};
260
261/* im_api core stuff. */
262void nogaim_init();
263G_MODULE_EXPORT GSList *get_connections();
264G_MODULE_EXPORT struct prpl *find_protocol( const char *name );
265/* When registering a new protocol, you should allocate space for a new prpl
266 * struct, initialize it (set the function pointers to point to your
267 * functions), finally call this function. */
268G_MODULE_EXPORT void register_protocol( struct prpl * );
269
270/* Connection management. */
271/* You will need this function in prpl->login() to get an im_connection from
272 * the account_t parameter. */
273G_MODULE_EXPORT struct im_connection *imcb_new( account_t *acc );
274G_MODULE_EXPORT void imc_free( struct im_connection *ic );
275/* Once you're connected, you should call this function, so that the user will
276 * see the success. */
277G_MODULE_EXPORT void imcb_connected( struct im_connection *ic );
278/* This can be used to disconnect when something went wrong (ie. read error
279 * from the server). You probably want to set the second parameter to TRUE. */
280G_MODULE_EXPORT void imc_logout( struct im_connection *ic, int allow_reconnect );
281
282/* Communicating with the user. */
283/* A printf()-like function to tell the user anything you want. */
284G_MODULE_EXPORT void imcb_log( struct im_connection *ic, char *format, ... ) G_GNUC_PRINTF( 2, 3 );
285/* To tell the user an error, ie. before logging out when an error occurs. */
286G_MODULE_EXPORT void imcb_error( struct im_connection *ic, char *format, ... ) G_GNUC_PRINTF( 2, 3 );
287
288/* To ask a your about something.
289 * - 'msg' is the question.
290 * - 'data' can be your custom struct - it will be passed to the callbacks.
291 * - 'doit' or 'dont' will be called depending of the answer of the user.
292 */
293G_MODULE_EXPORT void imcb_ask( struct im_connection *ic, char *msg, void *data, query_callback doit, query_callback dont );
294G_MODULE_EXPORT void imcb_ask_with_free( struct im_connection *ic, char *msg, void *data, query_callback doit, query_callback dont, query_callback myfree );
295
296/* Two common questions you may want to ask:
297 * - X added you to his contact list, allow?
298 * - X is not in your contact list, want to add?
299 */
300G_MODULE_EXPORT void imcb_ask_auth( struct im_connection *ic, const char *handle, const char *realname );
301G_MODULE_EXPORT void imcb_ask_add( struct im_connection *ic, const char *handle, const char *realname );
302
303/* Buddy management */
304/* This function should be called for each handle which are visible to the
305 * user, usually after a login, or if the user added a buddy and the IM
306 * server confirms that the add was successful. Don't forget to do this! */
307G_MODULE_EXPORT void imcb_add_buddy( struct im_connection *ic, const char *handle, const char *group );
308G_MODULE_EXPORT void imcb_remove_buddy( struct im_connection *ic, const char *handle, char *group );
309G_MODULE_EXPORT struct buddy *imcb_find_buddy( struct im_connection *ic, char *handle );
310G_MODULE_EXPORT void imcb_rename_buddy( struct im_connection *ic, const char *handle, const char *realname );
311G_MODULE_EXPORT void imcb_buddy_nick_hint( struct im_connection *ic, const char *handle, const char *nick );
312
313G_MODULE_EXPORT void imcb_buddy_typing( struct im_connection *ic, const char *handle, uint32_t flags );
314G_MODULE_EXPORT struct bee_user *imcb_buddy_by_handle( struct im_connection *ic, const char *handle );
315G_MODULE_EXPORT void imcb_clean_handle( struct im_connection *ic, char *handle );
316
317/* Actions, or whatever. */
318int imc_away_send_update( struct im_connection *ic );
319int imc_chat_msg( struct groupchat *c, char *msg, int flags );
320
321void imc_add_allow( struct im_connection *ic, char *handle );
322void imc_rem_allow( struct im_connection *ic, char *handle );
323void imc_add_block( struct im_connection *ic, char *handle );
324void imc_rem_block( struct im_connection *ic, char *handle );
325
326/* Misc. stuff */
327char *set_eval_timezone( set_t *set, char *value );
328gboolean auto_reconnect( gpointer data, gint fd, b_input_condition cond );
329void cancel_auto_reconnect( struct account *a );
330
331#endif
Note: See TracBrowser for help on using the repository browser.