@@ -150,14 +150,14 @@ Upgrading a plugin
150
150
------------------
151
151
152
152
The first thing to know about Annotator 2.0 is that we are retiring the use of
153
- the word "plugin". Our documentation and code refers to reusable pieces of code
154
- such as :func: `annotator.storage.http ` as "modules" . Modules are included into
155
- an :class: `~annotator.App `, and are able to register providers of named
153
+ the word "plugin". Our documentation and code refers to a reusable piece of code
154
+ such as :func: `annotator.storage.http ` as a :term: ` module ` . Modules are included
155
+ into an :class: `~annotator.App `, and are able to register providers of named
156
156
interfaces (such as "storage" or "notifier"), as well as providing runnable
157
- " hook functions" that the app calls at important moments. Annotator 1.2's
158
- lifecycle events (``beforeAnnotationCreated ``, ``annotationCreated ``, etc.) are
159
- still available as hooks, and it should be reasonably straightforward to migrate
160
- plugins that simply respond to lifecycle events.
157
+ :term: ` hook ` functions that are called at important moments. The lifecycle
158
+ events in Annotator 1.2 (``beforeAnnotationCreated ``, ``annotationCreated ``,
159
+ etc.) are still available as hooks, and it should be reasonably straightforward
160
+ to migrate plugins that simply respond to lifecycle events.
161
161
162
162
The second important observation is that Annotator 2.0 is written in JavaScript,
163
163
not CoffeeScript. You may continue to write modules in any dialect you like,
0 commit comments