Are we supposed to be able to use either files to work with this plugin or just the opentok.js included in this plugin?
3a. If we're just supposed to use the included file, are there any plans of updating the included opentok.js? (since it seems to be a bit out-of-date or out of sync with the one hosted on opentok)
Observed notes that led to the above questions:
From just trying to include them one at the time, it seems like the included opentok.js works (when using Intel XDK to compile an app) but the one hosted on opentok does not (as it requires to be loaded via http instead of file:// and the current Intel XDK framework only wants to load by file://)
However, sticking with the included opentok.js is worrisome since it seems like a lot of its stuff are deprecated or obsolete already (ie. the publisher object still uses .domId whereas the opentok's documents indicate it should be .id now)
This opentok.js is completely different from OpenTok's one. It is made to have a similar API but it doesn't support all of the same features. It has been completely rewritten to work as a bridge between the JS in the browser and OpenTok's iOS and Android SDKs. It was not written by the OpenTok JS team, it is a 3rd party open source project.
It's not currently following a versioning system but it should.
Only the opentok.js included in this plugin will work.
a. Yes we're aware of some of the issues, they have been filed in the issues list. If you find any other ones please add to the list. Also, feel free to chip in and fix some of the inconsistencies, we invite contributions from others using this plugin.
Some questions:
Observed notes that led to the above questions: