Skip to content

Kaltura Advanced Video Analytics Plugin for the Kaltura Player

License

Notifications You must be signed in to change notification settings

kaltura/playkit-js-kava

Repository files navigation

PlayKit JS Kava - Kaltura Advanced Video Analytics Plugin for the Kaltura Player JS

Build Status code style: prettier

PlayKit JS Kava plugin integrates Kava (Kaltura Advanced Video Analytics) with the Kaltura Player JS.

The main purpose of this plugin is to track and collect various events and data about the video player.

PlayKit JS Kava 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.

Installing

First, clone and run yarn to install dependencies:

git clone https://github.com/kaltura/playkit-js-kava.git
cd playkit-js-kava
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/kaltura-{ovp/tv}-player.js"></script>
<script type="text/javascript" src="/PATH/TO/FILE/playkit-kava.js"></script>
<div id="player-placeholder" style="height:360px; width:640px">
  <script type="text/javascript">
    var config = {
      targetId: 'player-placeholder',
      provider: {
        partnerId: {PARTNER_ID}
        ...
      },
      plugins: {
        kava: {
           ...
        }
       ...
      }
    ...
    };
    var player = KalturaPlayer.setup(config);
    player.loadMedia({
      entryId: '{ENTRY_ID}'
      ...
    });
  </script>
</div>

Documentation

Table of Contents

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