From ba224f382dfc02f187591a49b437d89973650e46 Mon Sep 17 00:00:00 2001 From: Andrew Manning Date: Sun, 28 Aug 2016 06:59:26 -0400 Subject: Remove definite article before $Projectname in docs --- doc/plugins.bb | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'doc/plugins.bb') diff --git a/doc/plugins.bb b/doc/plugins.bb index f2f0b04e8..a320de790 100644 --- a/doc/plugins.bb +++ b/doc/plugins.bb @@ -45,7 +45,7 @@ In our case, we'll call them randplace_load() and randplace_unload(), as that is pluginname_uninstall() [/code] -Next we'll talk about [b]hooks[/b]. Hooks are places in the $Projectname code where we allow plugins to do stuff. There are a [url=[baseurl]/help/hooklist]lot of these[/url], 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 [b]hooks[/b]. Hooks are places in $Projectname code where we allow plugins to do stuff. There are a [url=[baseurl]/help/hooklist]lot of these[/url], 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 'Zotlabs\Extend\Hook::register()' function. It typically 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 $Projectname installation), and the third is the function name of your handler function. So let's create our randplace_load() function right now. @@ -295,13 +295,13 @@ If you want to keep your plugin hidden from the siteinfo page, simply create a f ***Porting Friendica Plugins*** -The $Projectname uses a similar plugin architecture to the Friendica project. The authentication, identity, and permissions systems are completely different. Many Friendica can be ported reasonably easily by renaming a few functions - and then ensuring that the permissions model is adhered to. The functions which need to be renamed are: +$Projectname uses a similar plugin architecture to the Friendica project. The authentication, identity, and permissions systems are completely different. Many Friendica can be ported reasonably easily by renaming a few functions - and then ensuring that the permissions model is adhered to. The functions which need to be renamed are: [li] Friendica's pluginname_install() is pluginname_load()[/li] [li] Friendica's pluginname_uninstall() is pluginname_unload()[/li] -The $Projectname has _install and _uninstall functions but these are used differently. +$Projectname has _install and _uninstall functions but these are used differently. [li] Friendica's "plugin_settings" hook is called "feature_settings"[/li] -- cgit v1.2.3