comparison src/dbus-server.h @ 14035:8bda65b88e49

[gaim-migrate @ 16638] A bunch of small changes. Mostly remove "if not null" checks before calling g_free, g_list_free, g_slist_free and g_strdup. Also use g_list_foreach() to call g_free to free strings in an array. And some whitespace changes here and there. committer: Tailor Script <[e-mail]>

14034:0839a7b71325

#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 {

   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.
 */

    @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);

/**
 * Returns whether Gaim's D-BUS subsystem is up and running.  If it's
 * NOT running then gaim_dbus_dispatch_init() failed for some reason,

 */

#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.
*/

14035:8bda65b88e49

#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 {

   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.
 */

    @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);

/**
 * Returns whether Gaim's D-BUS subsystem is up and running.  If it's
 * NOT running then gaim_dbus_dispatch_init() failed for some reason,

 */

#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.
*/