Plugin extensibility (e.g. page transitions, reflow views, annotations, ...) about readium-shared-js

[danielweck]

Example (click-on-text for sign language):
ogoldbart3/readium-js@0a2135a

See here as well:
https://github.com/ishaangrover/ASL/blob/master/ASL

[dmitrym0]

Note that annotations support lives in EP's private fork, we're still working on contributing this but the amount of work is nontrivial. It would be interesting perhaps to consider refactoring it on top of a plugin architecture.. @jccr ?

[jccr]

A plugin architecture sounds good, as not everyone will want annotations (for example) as part of the whole codebase.

[danielweck]

Another example, MathML "protocol handler" for accessible readout:

https://wiki.benetech.org/display/MATH/Protocol+Handlers+for+External+Applications+to+Process+MathML

...using "MathML Cloud":
http://benetech.org/our-programs/literacy/born-accessible/mathml-cloud/

[danielweck]

Another suggestion from some user / developer feedback I got today:
LDAP (or other) server-stored user preferences, unique (human) reader identifier.

[danielweck]

See also:
#81

[danielweck]

Somewhat related: #151

[danielweck]

Closing, for two reasons:

1. there is a simple low-level context-agnostic "plugin framework" in the build system of readium-shared-js, see https://github.com/readium/readium-shared-js/wiki/Plugins + https://github.com/readium/readium-shared-js/tree/develop/plugins
2. this issue is too generic, some of the suggested plugin use-cases are higher-level (they require custom readium-js-viewer UI / UX implementations that the current plugin framework is not designed for, and there are no plans to provide fine-grained extension points other than the basic "PAGINATION_READY" kinds of events)