Mercurial > pidgin
annotate doc/plugin-ids.dox @ 15113:4a8c368df4ea
[gaim-migrate @ 17899]
Some touchups:
* If one of the parallel connection attempts fails immediately (i.e.
does not time out) then don't cancel the other one.
* Make sure we don't continue on to step 2 of the peer connection
process after we kick off the parallel gaim_proxy_connects(). It
looks like this would happen most of the time, because the
connect_timeout_timer would be added for the verified ip, so it
would NOT be added for the client ip, and so we wouldn't hit the
"return" call because it happens to be in the same block as the
second gaim_timeout_add() call.
* Add the connection timeout timer even if the gaim_proxy_connect() to
the verified ip returns NULL for some crazy reason.
I didn't actually test any of this. I should probably do that when
I get home.
committer: Tailor Script <tailor@pidgin.im>
| author | Mark Doliner <mark@kingant.net> |
|---|---|
| date | Wed, 06 Dec 2006 01:29:59 +0000 |
| parents | cf3eb9f311b2 |
| children | 1414e0e01dc5 |
| rev | line source |
|---|---|
| 7335 | 1 /** @page plugin-ids Plugin IDs |
| 2 | |
| 3 @section Introduction | |
| 4 Every plugin contains a unique identifier to prevent duplicate plugin | |
| 5 loading and conflicts. This, which will be called a plugin ID from here | |
| 6 on, must follow a specific format. This format categorizes a plugin and | |
| 7 makes duplicate IDs unlikely. | |
| 8 | |
| 9 | |
| 10 @section Format | |
| 11 The basic format of a plugin ID is as follows: | |
| 12 | |
| 13 <tt><i>type</i>-<i>username</i>-<i>pluginname</i></tt> | |
| 14 | |
| 15 The @em type indicator specifies the type of plugin. This must be one | |
| 16 of the following: | |
| 17 | |
| 18 - core - Core plugin, capable of being loaded in any program using | |
| 19 libgaim. It must not use any UI-specific code. | |
| 20 - prpl - Protocol plugin, providing additional protocols to | |
| 21 connect to. | |
| 22 - lopl - Loader plugin, which loads scripts as plugins (like Perl | |
| 23 or TCL). | |
| 24 - gtk - GTK+ 2.x plugin. It may use GTK+ code, but cannot use any | |
| 25 window toolkit code (such as X11 or Win32). | |
| 26 - gtk-x11 - GTK+ 2.x plugin using X11 code. | |
| 27 - gtk-win32 - GTK+ 2.x plugin using Win32 code. | |
| 28 - qpe - Gaim for Qtopia plugin. | |
| 29 | |
| 30 The @em username must be a unique identifier for that person. It | |
|
13863
cf3eb9f311b2
[gaim-migrate @ 16326]
Richard Laager <rlaager@wiktel.com>
parents:
7335
diff
changeset
|
31 @em should be your SourceForge ID. Do @em not leave this field |
| 7335 | 32 blank. |
| 33 | |
| 34 The @em pluginname is the name of your plugin. It can be whatever you like, | |
| 35 though it's common to keep it all lowercase. Do not use spaces! If you | |
| 36 want a space, use a '-'. Please do not put a version indicator in the ID. | |
| 37 The GaimPlugin structure already has a field for this. | |
| 38 | |
| 39 | |
| 40 @section plugin-db Plugin Database | |
| 41 Although it doesn't exist yet, in time there will be a plugin database | |
| 42 on the Gaim website, where users can download and install new plugins. | |
| 43 Plugins will be accessed by your plugin ID, which is one reason why it | |
| 44 must be unique. | |
| 45 | |
| 46 */ | |
| 47 | |
| 48 // vim: syntax=c tw=75 et |
