Expose and Simplify OT Engine access

[vinomaster]

The goal here is to enable web developers to consume our OT Engine as a separate library w/o using our Collaboration API.

The solution to this issue would be comprised of the following:

• Single JS file to be used to include all classes within the OT Engine (See Note 1)
• Build/Packaging of OT Engine as a separate library
• Update (See Note 2) and add new docs where necessary to address usage of OT Engine outside of OpenCoweb

Notes:

1. Tactically this can be done via JS includes; Strategically, we can address AMD and/or CommonJS loaders
2. As per existing docs we hide OT complexity: http://opencoweb.org/ocwdocs/intro/openg.html#a-final-word

[vinomaster]

As per Issue #147 we need to be able to deliver Java and JS packages of the OT Engine libraries.

[ccotter]

Current status (working on issue145 branch)

All OCW JS OT code has been moved into a new git repo opencoweb/coweb-jsoe.git. OCW now includes the OT code as a submodule.

Changes required

Several changes are in order:

• Changing developer setup and release process: https://github.com/opencoweb/coweb/wiki/New-developer-setup-with-coweb-jsoe.git
• Make announcements when the changes go into effect and a new OCW is released incorporating these changes.

[ccotter]

Branch issue145 has been merged into master. I'm going to close this issue as all items have been completed. Any new issues relating to this can be created as new issues.