Package Exports

@playkit-js/playkit-js-airplay
@playkit-js/playkit-js-airplay/dist/playkit-airplay.js

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@playkit-js/playkit-js-airplay) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

PlayKit JS AirPlay - Apple AirPlay Plugin for the Kaltura Player JS

PlayKit JS AirPlay plugin integrates AirPlay Button with the Kaltura Player JS.

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

Getting Started

Prerequisites

The plugin requires Kaltura Player JS to be loaded first.

Installing

First, clone and run yarn to install dependencies:

git clone https://github.com/kaltura/playkit-js-airplay.git
cd playkit-js-airplay
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

<!--PlayKit player-->
<script type="text/javascript" src="/PATH/TO/FILE/kaltura-{ovp/ott}-player.js"></script>
<!--PlayKit AirPlay plugin-->
<script type="text/javascript" src="/PATH/TO/FILE/playkit-airplay.js"></script>
<div id="player-placeholder" style="height:360px; width:640px">
  <script type="text/javascript">
    var config = {
      provider: {
        partnerId: {YOUR_PARTNER_ID}
        ...
      },
      ...
      plugins: {
        airplay: {}
      }
      ...
    };
    var player = KalturaPlayer.setup(config);
    player.play();
  </script>
</div>

Running the tests

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

yarn run test

You can test Safari browser:

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