Skip to content

Youbora analytics SDK plugin for the PlayKit JS Player

License

Notifications You must be signed in to change notification settings

kaltura/playkit-js-youbora

Repository files navigation

PlayKit JS Youbora - Youbora analytics SDK plugin for the PlayKit JS Player

Build Status code style: prettier

PlayKit JS Youbora plugin integrates Youbora analytics SDK with the PlayKit JS Player.

PlayKit JS Youbora is written in ECMAScript6, statically analysed using Flow and transpiled in ECMAScript5 using Babel.

Getting Started

Prerequisites

The plugin requires PlayKit JS Player to be loaded first.

The plugin uses the Youbora analytics SDK for HTML5.

Installing

First, clone and run yarn to install dependencies:

git clone https://github.com/kaltura/playkit-js-youbora.git
cd playkit-js-youbora
yarn install

Building

Then, build the player

yarn run build

Embed the library in your test page

Finally, add the bundle as a script tag in your page, and initialize the player

<script type="text/javascript" src="/PATH/TO/FILE/playkit.js"></script>
<script type="text/javascript" src="/PATH/TO/FILE/playkit-youbora.js"></script>
<div id="player-placeholder" style="height:360px; width:640px">
  <script type="text/javascript">
    var playerContainer = document.querySelector("#player-placeholder");
    var config = {
     ...
     plugins: {
       youbora: {
         options: {
           accountCode: "YOUR_ACCOUNT_CODE"
         }
       }
     }
     ...
    };
    var player = playkit.core.loadPlayer(config);
    playerContainer.appendChild(player.getView());
    player.play();
  </script>
</div>

Configuration

This plugin configuration reflects Youbora options, For full Youbora options see: https://documentation.npaw.com/npaw-integration/docs/setting-options-and-metadata

Running the tests

Tests can be run locally via Karma, which will run on Chrome, Firefox and Safari

yarn run test

You can test individual browsers:

yarn run test:chrome
yarn run test:firefox
yarn run test:safari

And coding style tests

We use ESLint recommended set with some additions for enforcing Flow types and other rules.

See ESLint config for full configuration.

We also use .editorconfig to maintain consistent coding styles and settings, please make sure you comply with the styling.

Compatibility

TBD

Contributing

Please read CONTRIBUTING.md for details on our code of conduct, and the process for submitting pull requests to us.

Versioning

We use SemVer for versioning. For the versions available, see the tags on this repository.

License

This project is licensed under the AGPL-3.0 License - see the LICENSE.md file for details