Mercurial > pidgin
view src/dbus-server.h @ 12116:e75ef7aa913e
[gaim-migrate @ 14416]
" This patch implements a replacement for the queuing
system from 1.x. It also obsoletes a previous patch
[#1338873] I submitted to prioritize the unseen states
in gtk conversations.
The attached envelope.png is ripped from the
msgunread.png already included in gaim. It should be
dropped in the pixmaps directory (Makefile.am is
updated accordingly in this patch).
The two separate queuing preferences from 1.x, queuing
messages while away and queuing all new messages (from
docklet), are replaced with a single 3-way preference
for conversations. The new preference is "Hide new IM
conversations". This preference can be set to never,
away and always.
When a gtk conversation is created, it may be placed in
a hidden conversation window instead of being placed
normally. This decision is based upon the preference
and possibly the away state of the account the
conversation is being created for. This *will* effect
conversations the user explicitly requests to be
created, so in these cases the caller must be sure to
present the conversation to the user, using
gaim_gtkconv_present_conversation(). This is done
already in gtkdialogs.c which handles creating
conversations requested by the user from gaim proper
(menus, double-clicking on budy in blist, etc.).
The main advantage to not queuing messages is that the
conversations exist, the message is written to the
conversation (and logged if appropriate) and the unseen
state is set on the conversation. This means no
additional features are needed to track whether there
are queued messages or not, just use the unseen state
on conversations.
Since conversations may not be visible (messages
"queued"), gaim proper needs some notification that
there are messages waiting. I opted for a menutray icon
that shows up when an im conversation has an unseen
message. Clicking this icon will focus (and show if
hidden) the first conversation with an unseen message.
This is essentially the same behavior of the docklet in
cvs right now, except that the icon is only visible
when there is a conversation with an unread message.
The api that is added is flexible enough to allow
either the docklet or the new blist menutray icon to be
visible for conversations of any/all types and for
unseen messages >= any state. Currently they are set to
only IM conversations and only unseen states >= TEXT
(system messages and no log messages will not trigger
blinking the docklet or showing the blist tray icon),
but these could be made preferences relatively easily
in the future. Other plugins could probably benefit as
well: gaim_gtk_conversations_get_first_unseen().
There is probably some limit to comment size, so I'll
stop rambling now. If anyone has more
questions/comments, catch me in #gaim, here or on
gaim-devel."
committer: Tailor Script <tailor@pidgin.im>
author | Luke Schierer <lschiere@pidgin.im> |
---|---|
date | Wed, 16 Nov 2005 18:17:01 +0000 |
parents | c9312177821a |
children | 2078f65a8e98 |
line wrap: on
line source
/** * @file dbus-server.h Gaim DBUS Server * @ingroup core * * gaim * * Gaim is the legal property of its developers, whose names are too numerous * to list here. Please refer to the COPYRIGHT file distributed with this * source distribution. * * This program is free software; you can redistribute it and/or modify * it under the terms of the GNU General Public License as published by * the Free Software Foundation; either version 2 of the License, or * (at your option) any later version. * * This program is distributed in the hope that it will be useful, * but WITHOUT ANY WARRANTY; without even the implied warranty of * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the * GNU General Public License for more details. * * You should have received a copy of the GNU General Public License * along with this program; if not, write to the Free Software * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA * */ #ifndef _GAIM_DBUS_SERVER_H_ #define _GAIM_DBUS_SERVER_H_ #include "value.h" G_BEGIN_DECLS /** Types of pointers are identified by the ADDRESS of a GaimDbusType object. This way, plugins can easily access types defined in gaim proper as well as introduce their own types that will not conflict with those introduced by other plugins. The structure GaimDbusType has only one element (GaimDBusType::parent), a contains a pointer to the parent type, or @c NULL if the type has no parent. Parent means the same as the base class in object oriented programming. */ typedef struct _GaimDBusType GaimDBusType; struct _GaimDBusType { GaimDBusType *parent; }; /* By convesion, the GaimDBusType variable representing each structure GaimSomeStructure has the name GAIM_DBUS_TYPE_GaimSomeStructure. The following macros facilitate defining such variables #GAIM_DBUS_DECLARE_TYPE declares an extern variable representing a given type, for use in header files. #GAIM_DBUS_DEFINE_TYPE defines a variable representing a given type, use in .c files. It defines a new type without a parent; for types with a parent use #GAIM_DBUS_DEFINE_INHERITING_TYPE. */ #define GAIM_DBUS_TYPE(type) (&GAIM_DBUS_TYPE_##type) #define GAIM_DBUS_DECLARE_TYPE(type) \ extern GaimDBusType GAIM_DBUS_TYPE_##type; #define GAIM_DBUS_DEFINE_TYPE(type) \ GaimDBusType GAIM_DBUS_TYPE_##type = { NULL }; #define GAIM_DBUS_DEFINE_INHERITING_TYPE(type, parent) \ GaimDBusType GAIM_DBUS_TYPE_##type = { GAIM_DBUS_TYPE(parent) }; /** Initializes gaim dbus pointer registration engine. Remote dbus applications need a way of addressing objects exposed by gaim to the outside world. In gaim itself, these objects (such as GaimBuddy and company) are identified by pointers. The gaim dbus pointer registration engine converts pointers to handles and back. In order for an object to participate in the scheme, it must register itself and its type with the engine. This registration allocates an integer id which can be resolved to the pointer and back. Handles are not persistent. They are reissued every time gaim is started. This is not good; external applications that use gaim should work even whether gaim was restarted in the middle of the interaction. Pointer registration is only a temporary solution. When GaimBuddy and similar structures have been converted into gobjects, this registration will be done automatically by objects themselves. By the way, this kind of object-handle translation should be so common that there must be a library (maybe even glib) that implements it. I feel a bit like reinventing the wheel here. */ void gaim_dbus_init_ids(void); /** Registers a typed pointer. @param node The pointer to register. @param type Type of that pointer. */ void gaim_dbus_register_pointer(gpointer node, GaimDBusType *type); /** Unregisters a pointer previously registered with gaim_dbus_register_pointer. @param node The pointer to register. */ void gaim_dbus_unregister_pointer(gpointer node); /** Emits a dbus signal. @param name The name of the signal ("bla-bla-blaa") @param num_values The number of parameters. @param values Array of pointers to #GaimValue objects representing the types of the parameters. @param vargs A va_list containing the actual parameters. */ void gaim_dbus_signal_emit_gaim(const char *name, int num_values, GaimValue **values, va_list vargs); /** * Starts the gaim DBUS server. It is responsible for handling DBUS * requests from other applications. * * @return TRUE if successful, FALSE otherwise. */ gboolean gaim_dbus_init(void); /** Macro #DBUS_EXPORT expands to nothing. It is used to indicate to the dbus-analize-functions.py script that the given function should be available to other applications through DBUS. If dbus-analize-functions.py is run without the "--export-only" option, this prefix is ignored. */ #define DBUS_EXPORT /* Here we include the list of #GAIM_DBUS_DECLARE_TYPE statements for all structs defined in gaim. This file has been generated by the #dbus-analize-types.py script. */ #include "dbus-types.h" G_END_DECLS #endif /* _GAIM_DBUS_SERVER_H_ */