Action Links

[Gary Kramlich]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Richard Laager wrote:

<snip>

> You can currently do this by overriding the relevant UI op. Really,
> though, you should write a patch to libpurple that adds the ability for
> plugins to register URI schemes. Then, libpurple would check those
> before passing the URL to the UI. If it matched, the plugin would get
> the first crack at handling the URI. It could return a boolean to tell
> libpurple whether or not to continue passing it to the UI.
> 
> If you need any help with the concepts, feel free to ask.
> 
> Richard

Stacking may be desired as well.  ie: someone sends http://pidgin-bug/2,
 then the handler that was registered on top can expand pidgin-bug to
developer.pidgin.im/ticket/ and get the correct url.  This could also be
done via a handler, and that would probably be a lot easier to
implement.  So whatever, just food for thought.

- --
Gary Kramlich <grim at reaperworld.com>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHUeNXdf4lmqisgDIRAhfKAJ4gS4Itv0BHUVQKpY1JtVlP63viBQCfUDCc
vc4TNzcqb7qXcafxMEZnngY=
=MCM0
-----END PGP SIGNATURE-----