view doc/plugin-ids.dox @ 9328:33e6b2b92cfe

[gaim-migrate @ 10136] "Initial Comment: This fixes a few more bugs, patches up some memory leaks, and adds things to the todo list: Uncomment and fix handle_unknown to print debug info for unhandled zephyrs. Fix triple_subset for some odd cases class "*" and recipient "*" only match themselves. Notifies when a message to chat fails. Zephyrs to <message,personal,recipient> (where recipient!=username), now get treated as chat messages, instead of IM's. Incoming IM's from user@thisrealm appear from user instead of user@thisrealm. Sets the default sending instance for chats to "PERSONAL" if not specified or set to * (wildcard) for compatibility with zwrite. Add miscellaneous code comments. Joining chats from a buddy list does the right thing when the instance or recipient aren't specified. When joining chats from a dialog box (or buddy list), new messages sent from that chat window caused a second nonfunctional window for the same chat to popup. This is fixed here." --Arun A Tharuvai committer: Tailor Script <tailor@pidgin.im>
author Luke Schierer <lschiere@pidgin.im>
date Sun, 20 Jun 2004 14:46:24 +0000
parents 3c3039aa7259
children cf3eb9f311b2
line wrap: on
line source

/** @page plugin-ids Plugin IDs

 @section Introduction
  Every plugin contains a unique identifier to prevent duplicate plugin
  loading and conflicts. This, which will be called a plugin ID from here
  on, must follow a specific format. This format categorizes a plugin and
  makes duplicate IDs unlikely.


 @section Format
  The basic format of a plugin ID is as follows:

  <tt><i>type</i>-<i>username</i>-<i>pluginname</i></tt>

  The @em type indicator specifies the type of plugin. This must be one
  of the following:

    - core      - Core plugin, capable of being loaded in any program using
                  libgaim. It must not use any UI-specific code.
    - prpl      - Protocol plugin, providing additional protocols to
                  connect to.
    - lopl      - Loader plugin, which loads scripts as plugins (like Perl
                  or TCL).
    - gtk       - GTK+ 2.x plugin. It may use GTK+ code, but cannot use any
                  window toolkit code (such as X11 or Win32).
    - gtk-x11   - GTK+ 2.x plugin using X11 code.
    - gtk-win32 - GTK+ 2.x plugin using Win32 code.
    - qpe       - Gaim for Qtopia plugin.

  The @em username must be a unique identifier for that person. It
  @em should be your Gaim website user ID
  (registered <a href="http://gaim.sourceforge.net/register.php">here</a>).
  If for some reason you cannot register there (it shouldn't be a
  problem!), you can use your SourceForge ID. Do @em not leave this field
  blank.

  The @em pluginname is the name of your plugin. It can be whatever you like,
  though it's common to keep it all lowercase. Do not use spaces! If you
  want a space, use a '-'. Please do not put a version indicator in the ID.
  The GaimPlugin structure already has a field for this.


 @section plugin-db Plugin Database
  Although it doesn't exist yet, in time there will be a plugin database
  on the Gaim website, where users can download and install new plugins.
  Plugins will be accessed by your plugin ID, which is one reason why it
  must be unique. 

 */

// vim: syntax=c tw=75 et