aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorfriendica <info@friendica.com>2013-10-18 15:52:17 -0700
committerfriendica <info@friendica.com>2013-10-18 15:52:17 -0700
commit7e5570aa9c01203e9a876ccda8366c6ffb315988 (patch)
tree3009fd607e352c5407cf63a63550f82b4ef23cbc
parent4ce948731aa2a927758a74d3cdf3d113cbddf4b0 (diff)
downloadvolse-hubzilla-7e5570aa9c01203e9a876ccda8366c6ffb315988.tar.gz
volse-hubzilla-7e5570aa9c01203e9a876ccda8366c6ffb315988.tar.bz2
volse-hubzilla-7e5570aa9c01203e9a876ccda8366c6ffb315988.zip
add hooklist to plugin page
-rw-r--r--doc/Plugins.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/Plugins.md b/doc/Plugins.md
index 1b5f57240..f22f1b09d 100644
--- a/doc/Plugins.md
+++ b/doc/Plugins.md
@@ -47,7 +47,7 @@ In our case, we'll call them randplace_load() and randplace_unload(), as that is
* pluginname_uninstall()
-Next we'll talk about **hooks**. Hooks are places in the Red Matrix code where we allow plugins to do stuff. There are a lot of these, and they each have a name. What we normally do is use the pluginname_load() function to register a "handler function" for any hooks you are interested in. Then when any of these hooks are triggered, your code will be called.
+Next we'll talk about **hooks**. Hooks are places in the Red Matrix code where we allow plugins to do stuff. There are a [lot of these](help/Hooks), and they each have a name. What we normally do is use the pluginname_load() function to register a "handler function" for any hooks you are interested in. Then when any of these hooks are triggered, your code will be called.
We register hook handlers with the 'register_hook()' function. It takes 3 arguments. The first is the hook we wish to catch, the second is the filename of the file to find our handler function (relative to the base of your Red Matrix installation), and the third is the function name of your handler function. So let's create our randplace_load() function right now.