mirror of
https://github.com/YunoHost-Apps/etherpad_ynh.git
synced 2024-09-03 18:36:10 +02:00
119 lines
6.8 KiB
Markdown
Executable file
119 lines
6.8 KiB
Markdown
Executable file
# Plugins
|
|
Etherpad allows you to extend its functionality with plugins. A plugin registers hooks (functions) for certain events (thus certain features) in Etherpad-lite to execute its own functionality based on these events.
|
|
|
|
Publicly available plugins can be found in the npm registry (see <http://npmjs.org>). Etherpad-lite's naming convention for plugins is to prefix your plugins with `ep_`. So, e.g. it's `ep_flubberworms`. Thus you can install plugins from npm, using `npm install ep_flubberworm` in etherpad-lite's root directory.
|
|
|
|
You can also browse to `http://yourEtherpadInstan.ce/admin/plugins`, which will list all installed plugins and those available on npm. It even provides functionality to search through all available plugins.
|
|
|
|
## Folder structure
|
|
A basic plugin usually has the following folder structure:
|
|
```
|
|
ep_<plugin>/
|
|
| static/
|
|
| templates/
|
|
| locales/
|
|
+ ep.json
|
|
+ package.json
|
|
```
|
|
If your plugin includes client-side hooks, put them in `static/js/`. If you're adding in CSS or image files, you should put those files in `static/css/ `and `static/image/`, respectively, and templates go into `templates/`. Translations go into `locales/`
|
|
|
|
A Standard directory structure like this makes it easier to navigate through your code. That said, do note, that this is not actually *required* to make your plugin run. If you want to make use of our i18n system, you need to put your translations into `locales/`, though, in order to have them intergated. (See "Localization" for more info on how to localize your plugin)
|
|
|
|
## Plugin definition
|
|
Your plugin definition goes into `ep.json`. In this file you register your hooks, indicate the parts of your plugin and the order of execution. (A documentation of all available events to hook into can be found in chapter [hooks](#all_hooks).)
|
|
|
|
A hook registration is a pairs of a hook name and a function reference (filename to require() + exported function name)
|
|
|
|
```json
|
|
{
|
|
"parts": [
|
|
{
|
|
"name": "nameThisPartHoweverYouWant",
|
|
"hooks": {
|
|
"authenticate" : "ep_<plugin>/<file>:FUNCTIONNAME1",
|
|
"expressCreateServer": "ep_<plugin>/<file>:FUNCTIONNAME2"
|
|
},
|
|
"client_hooks": {
|
|
"acePopulateDOMLine": "ep_plugin/<file>:FUNCTIONNAME3"
|
|
}
|
|
}
|
|
]
|
|
}
|
|
```
|
|
|
|
Etherpad-lite will expect the part of the hook definition before the colon to be a javascript file and will try to require it. The part after the colon is expected to be a valid function identifier of that module. So, you have to export your hooks, using [`module.exports`](http://nodejs.org/docs/latest/api/modules.html#modules_modules) and register it in `ep.json` as `ep_<plugin>/path/to/<file>:FUNCTIONNAME`.
|
|
You can omit the `FUNCTIONNAME` part, if the exported function has got the same name as the hook. So `"authorize" : "ep_flubberworm/foo"` will call the function `exports.authorize` in `ep_flubberworm/foo.js`
|
|
|
|
### Client hooks and server hooks
|
|
There are server hooks, which will be executed on the server (e.g. `expressCreateServer`), and there are client hooks, which are executed on the client (e.g. `acePopulateDomLine`). Be sure to not make assumptions about the environment your code is running in, e.g. don't try to access `process`, if you know your code will be run on the client, and likewise, don't try to access `window` on the server...
|
|
|
|
### Parts
|
|
As your plugins become more and more complex, you will find yourself in the need to manage dependencies between plugins. E.g. you want the hooks of a certain plugin to be executed before (or after) yours. You can also manage these dependencies in your plugin definition file `ep.json`:
|
|
|
|
```javascript
|
|
{
|
|
"parts": [
|
|
{
|
|
"name": "onepart",
|
|
"pre": [],
|
|
"post": ["ep_onemoreplugin/partone"]
|
|
"hooks": {
|
|
"storeBar": "ep_monospace/plugin:storeBar",
|
|
"getFoo": "ep_monospace/plugin:getFoo",
|
|
}
|
|
},
|
|
{
|
|
"name": "otherpart",
|
|
"pre": ["ep_my_example/somepart", "ep_otherplugin/main"],
|
|
"post": [],
|
|
"hooks": {
|
|
"someEvent": "ep_my_example/otherpart:someEvent",
|
|
"another": "ep_my_example/otherpart:another"
|
|
}
|
|
}
|
|
]
|
|
}
|
|
```
|
|
|
|
Usually a plugin will add only one functionality at a time, so it will probably only use one `part` definition to register its hooks. However, sometimes you have to put different (unrelated) functionalities into one plugin. For this you will want use parts, so other plugins can depend on them.
|
|
|
|
#### pre/post
|
|
The `"pre"` and `"post"` definitions, affect the order in which parts of a plugin are executed. This ensures that plugins and their hooks are executed in the correct order.
|
|
|
|
`"pre"` lists parts that must be executed *before* the defining part. `"post"` lists parts that must be executed *after* the defining part.
|
|
|
|
You can, on a basic level, think of this as double-ended dependency listing. If you have a dependency on another plugin, you can make sure it loads before yours by putting it in `"pre"`. If you are setting up things that might need to be used by a plugin later, you can ensure proper order by putting it in `"post"`.
|
|
|
|
Note that it would be far more sane to use `"pre"` in almost any case, but if you want to change config variables for another plugin, or maybe modify its environment, `"post"` could definitely be useful.
|
|
|
|
Also, note that dependencies should *also* be listed in your package.json, so they can be `npm install`'d automagically when your plugin gets installed.
|
|
|
|
## Package definition
|
|
Your plugin must also contain a [package definition file](http://npmjs.org/doc/json.html), called package.json, in the project root - this file contains various metadata relevant to your plugin, such as the name and version number, author, project hompage, contributors, a short description, etc. If you publish your plugin on npm, these metadata are used for package search etc., but it's necessary for Etherpad-lite plugins, even if you don't publish your plugin.
|
|
|
|
```json
|
|
{
|
|
"name": "ep_PLUGINNAME",
|
|
"version": "0.0.1",
|
|
"description": "DESCRIPTION",
|
|
"author": "USERNAME (REAL NAME) <MAIL@EXAMPLE.COM>",
|
|
"contributors": [],
|
|
"dependencies": {"MODULE": "0.3.20"},
|
|
"engines": { "node": ">= 0.6.0"}
|
|
}
|
|
```
|
|
|
|
## Templates
|
|
If your plugin adds or modifies the front end HTML (e.g. adding buttons or changing their functions), you should put the necessary HTML code for such operations in `templates/`, in files of type ".ejs", since Etherpad uses EJS for HTML templating. See the following link for more information about EJS: <https://github.com/visionmedia/ejs>.
|
|
|
|
## Writing and running front-end tests for your plugin
|
|
|
|
Etherpad allows you to easily create front-end tests for plugins.
|
|
|
|
1. Create a new folder
|
|
```
|
|
%your_plugin%/static/tests/frontend/specs
|
|
```
|
|
2. Put your spec file in here (Example spec files are visible in %etherpad_root_folder%/frontend/tests/specs)
|
|
|
|
3. Visit http://yourserver.com/frontend/tests your front-end tests will run.
|