npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@playkit-js/playkit-js-vr

v2.1.0

Published

[![Build Status](https://github.com/kaltura/playkit-js-vr/actions/workflows/run_canary_full_flow.yaml/badge.svg)](https://github.com/playkit-js-vr/actions/workflows/run_canary_full_flow.yaml) [![code style: prettier](https://img.shields.io/badge/code_styl

Downloads

27

Readme

PlayKit JS VR - VR plugin for the PlayKit JS Player

Build Status code style: prettier

PlayKit JS VR 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-vr.git
cd playkit-js-vr
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>
<!--PlayKit player-->
<script type="text/javascript" src="/PATH/TO/FILE/playkit-vr.js"></script>
<!--PlayKit VR plugin-->
<div id="player-placeholder" style="height:360px; width:640px">
  <script type="text/javascript">
    var playerContainer = document.querySelector("#player-placeholder");
    var config = {
     ...
     plugins: {
       vr: {
         toggleStereo: true
       }
     }
     ...
    };
    var player = playkit.core.loadPlayer(config);
    playerContainer.appendChild(player.getView());
    player.play();
  </script>
</div>

Documentation

The Kaltura Player supports 360° video in both desktop and mobile device for any kind of motion: mouse, touch, device motion and keyboard keys.

This plugin is depended on three.js library.

The player will be informed that it deals with 360/VR media by populating attributes in the sources object which is part of the kaltura player config it might be populted using providers or the app itself)

  • metadata object must contain "tags": "360" and "vr": {} object which is not null.

in case app is using setMedia instead of load media tags and vr for 360 plyback these attribues are expected to be populated by app

Media Sources Example

{
  "sources": {
    "options": {},
    "metadata": {
      "tags": "360"
    },
    "hls": [...],
    "dash": ...],
    "id": "",
    "duration": 362,
    "type": "Vod",
    "poster": "",
    "dvr": false,
    "vr": {},
    "captions": []
  }
}
The 360/VR plugin exposes some attribures from plugin configurations:
  • Player will load on stereo mode

  • Enable toggle vr/stereo mode button.

example

  • Change the sensitivity of the touch motion using moveMultiplier attribute. by default is 0.15.

  • Change the sensitivity the device motion itself, using deviceMotionMultiplier attribute. by default is 1.

  • Change the camera options - The projection mode is designed to mimic the way the human eye sees. It is the most common projection mode used for rendering a 3D scene. CameraOptions

plugins: {
...
"vr": { 
      "startInStereo": false,     
      "toggleStereo": false,     
      "moveMultiplier": 0.15,
      "deviceMotionMultiplier": 1,
      "cameraOptions": {
        "fov": 75,
        "aspect": 1.777, // (width/height)
        "near": 0.1,
        "far": 1000
      },
    },
}    
VR Plugin Player Event
  • VR_STEREO_MODE_CHANGED - this event will be fired once user click on the vr icon and changes the playback state from VR to STEREO mode.
VR Plugin Player Error code
  • VR_NOT_SUPPORTED - this event will be fired once the device used for 360/VR playback does not support this mode.

Configuration

  • In the following example you can change the plugin attributes and get the feeling what each attribute does.

VR Plugin Example

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