Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

READ ME: Please see okfn's fork, which is now the primary development fork.

branch: master

This branch is 0 commits ahead and 0 commits behind master

Fetching latest commit…

Octocat-spinner-32-eaf2f5

Cannot retrieve the latest commit at this time

Octocat-spinner-32 contrib
Octocat-spinner-32 css
Octocat-spinner-32 example
Octocat-spinner-32 img
Octocat-spinner-32 lib
Octocat-spinner-32 pkg
Octocat-spinner-32 src
Octocat-spinner-32 test
Octocat-spinner-32 tools
Octocat-spinner-32 .gitignore
Octocat-spinner-32 Cakefile
Octocat-spinner-32 LICENSE
Octocat-spinner-32 LICENSE-GPL
Octocat-spinner-32 LICENSE-MIT
Octocat-spinner-32 README.markdown
Octocat-spinner-32 demo.html
Octocat-spinner-32 dev.html
Octocat-spinner-32 dev.xhtml
Octocat-spinner-32 markup.html
Octocat-spinner-32 package.json
README.markdown

Annotator

Annotator is a web annotation system. Loaded into a webpage, it provides the user with tools to annotate text (and other elements) in the page. For a simple demonstration, download a tagged release of Annotator and open demo.html.

The Annotator project also has a simple but powerful plugin architecture. While the core annotator code does the bare minimum, it is easily extended with plugins that perform such tasks as:

  • serialization: the Store plugin saves all your annotations to a REST API backend (see the Flask store for an example)
  • authentication and authorization: the Auth and Permissions plugins allow you to decouple the storage of your annotations from the website on which the annotation happens. In practice, this means that users could edit pages across the web, with all their annotations being saved to one server.
  • prettification: the Markdown plugin renders all annotation text as Markdown
  • tagging: the Tags plugin allows you to tag individual annotations

Usage

To use Annotator, it's easiest to download a tagged release.

In a tagged release, the pkg/ directory will contain all the files you need to get going. The most important are annotator.min.js, which contains the core Annotator code, and annotator.min.css, which contains all the CSS and embedded images for the annotator.

Annotator requires jQuery and an implementation of JSON.parse and JSON.stringify. In short, the quickest way to get going with annotator is to include the following in the <head> of your document (paths relative to the repository root):

<script src='lib/vendor/jquery.js'></script>
<script src='lib/vendor/json2.js'></script>

<script src='pkg/annotator.min.js'></script>
<link rel='stylesheet' href='pkg/annotator.min.css'>

You can then initialize Annotator for the whole document by including the following at the end of the <body> tag:

<script>
  $(document.body).annotator()
</script>

See demo.html for an example how to load and interact with plugins.

Writing Plugins

As mentioned, Annotator has a simple but powerful plugin architecture. In order to write your own plugin, you need only add your plugin to the Annotator.Plugin object, ensuring that the first argument to the constructor is a DOM Element, and the second is an "options" object. Below is a simple Hello World plugin:

Annotator.Plugin.HelloWorld = (function() {

  function HelloWorld(element, options) {
    this.element = element;
    this.options = options;
    console.log("Hello World!");
  }

  HelloWorld.prototype.pluginInit = function() {
    console.log("Initialized with annotator: ", this.annotator);
  };

  return HelloWorld;
})();

Other than the constructor, the only "special" method is pluginInit, which is called after the Annotator has constructed the plugin, and set pluginInstance.annotator to itself. In order to load this plugin into an existing annotator, you would call addPlugin("HelloWorld"). For example:

$(document.body).annotator()
                .annotator('addPlugin', 'HelloWorld')

Look at the existing plugins to get a feel for how they work. The Markdown plugin is a good place to start.

Useful events are triggered on the Annotator element (passed to the constructor of the plugin):

  • annotationsLoaded(annotations): called when annotations are loaded into the DOM. Provides an array of all annotations.
  • beforeAnnotationCreated(annotation): called immediately before an annotation is created. If you need to modify the annotation before it is saved to the server by the Store plugin, use this event.
  • annotationCreated(annotation): called when the annotation is created. Used by the Store plugin to save new annotations.
  • beforeAnnotationUpdated(annotation): as above, but just before an existing annotation is saved.
  • annotationUpdated(annotation): as above, but for an existing annotation which has just been edited.
  • annotationDeleted(annotation): called when the user deletes an annotation.
  • annotationEditorShown(editor, annotation): called when the annotation editor is presented to the user. Allows a plugin to add extra form fields. See the Tags plugin for an example of its use.
  • annotationEditorHidden(editor): called when the annotation editor is hidden, both when submitted and when editing is cancelled.
  • annotationEditorSubmit(editor, annotation): called when the annotation editor is submitted.
  • annotationViewerShown(viewer, annotations): called when the annotation viewer is displayed provides the annotations being displayed
  • annotationViewerTextField(field, annotation): called when the text field displaying the annotation in the viewer is created

Development

If you wish to develop annotator, you'll need to have a working installation of Node.js (v0.2.x). I'd highly recommend installing both Node.js and the Node Package Manager, after which you can run the following to get up and running:

$ npm install .

In order to run the rake package task with JavaScript and CSS minification you'll need the yui-compressor gem installed:

$ gem install yui-compressor

If that worked, you should be able to run the tests:

$ cake test
Started
.....................................................

Finished in 0.385 seconds
18 tests, 85 assertions, 0 failures

The cake command is provided by CoffeeScript. Note that some tests may fail, due to brokenness in jsdom. There should be a note at the end of the output for that command informing you if we're expecting any tests to fail. The reason we don't simply comment these tests out until jsdom is fixed is that the tests can also be run by opening test/runner.html in a browser.

The Annotator source is found in src/, and is written in CoffeeScript, which is a little language that compiles to Javascript. See the CoffeeScript website for more information. For ease of development, you can run a watcher (cake watch) that will notice any changes you make in src/ and compile them into lib/.

dev.html loads the raw development files from lib/ and can be useful when developing.

The tests are to be found in test/spec/, and use Jasmine to support a BDD process.

For inline documentation we use TomDoc. It's a Ruby specification but it also works nicely with CoffeeScript.

Something went wrong with that request. Please try again.