Player example
Drag the scrollbar below the thumbnail images to navigate through the videos. Select a video to play the video in a lightbox container. With the lightbox displayed, select the Close link to hide the lightbox container.
See the Pen 18152-lightbox-scroller by Brightcove Learning Services (@bcls1969) on CodePen.
Source code
View the complete solution on GitHub.
See the Pen 18152-lightbox-scroller-bcplayer by Brightcove Learning Services (@bcls1969) on CodePen.
Source code
View the complete solution on GitHub.
Using the CodePen
Here are some tips to effectively use the above CodePen:
- Toggle the actual display of the player by clicking the Result button.
- Click the HTML/CSS/JS buttons to display ONE of the code types.
- Later in this document the logic, flow and styling used in the application will be discussed in the Player/HTML configuration, Application flow and Application styling sections. The best way to follow along with the information in those sections is to:
- Click the EDIT ON CODEPEN button in the CodePen and have the code available in one browser/browser tab.
- In CodePen, adjust what code you want displayed. You can change the width of different code sections within CodePen.
- View the Player/HTML configuration, Application flow and/or Application styling sections in another browser/browser tab. You will now be able to follow the code explanations and at the same time view the code.
Development sequence
Here is the recommended development sequence:
- Use the In-Page embed player implementation to test the functionality of your player, plugin and CSS (if CSS is needed)
- Put the plugin's JavaScript and CSS into separate files for local testing
- Deploy the plugin code and CSS to your server once you have worked out any errors
- Use Studio to add the plugin and CSS to your player
- Replace the In-Page embed player implementation if you determine that the iframe implementation is a better fit (detailed in next section)
For details about these steps, review the Step-by-Step: Plugin Development guide.
iframe or In-Page embed
When developing enhancements for the Brightcove Player you will need to decide if the code is a best fit for the iframe or In-Page embed implementation. The best practice recommendation is to build a plugin for use with an iframe implementation. The advantages of using the iframe player are:
- No collisions with existing JavaScript and/or CSS
- Automatically responsive
- The iframe eases use in social media apps (or whenever the video will need to "travel" into other apps)
Although integrating the In-Page embed player can be more complex, there are times when you will plan your code around that implementation. To generalize, this approach is best when the containing page needs to communicate to the player. Specifically, here are some examples:
- Code in the containing page needs to listen for and act on player events
- The player uses styles from the containing page
- The iframe will cause app logic to fail, like a redirect from the containing page
Even if your final implementation does not use the iframe code, you can still use the In-Page embed code with a plugin for your JavaScript and a separate file for your CSS. This encapsulates your logic so that you can easily use it in multiple players.
API/Plugin resources used
API Methods | API Events |
---|---|
playlist() | loadedmetadata |
playlist.currentItem() | |
play() | |
pause() |
Player/HTML configuration
This section details any special configuration needed during player creation. In addition, other HTML elements that must be added to the page, beyond the in-page embed player implementation code, are described.
Player configuration
No special configuration is required for the Brightcove Player you create for this sample.
Other HTML
Add a <div>
container to define the horizontal scroller to hold a set of video poster images and a container for the lightbox player. Also, define the close button for the lightbox.
Remember to add the id
attribute to the video-js
tag in the player embed code.
<video-js id="myPlayerID"
...
Application flow
The basic logic behind this application is:
- Build the horizontal playlist scroller.
- Play the selected video in the lightbox.
- Close the lightbox.
Build horizontal scroller
Find the code which is labeled:
// +++ Build horizontal scroller +++
Get the playlist data currently loaded in the player, and build the horizontal video poster scroller.
Play selected video
Find the code which is labeled:
// +++ Play selected video +++
When a poster image in the scroller is selected, then load the associated video into the player and start playback. Open the lightbox player with the playing video.
Close lightbox
Find the code which is labeled:
// +++ Close lightbox +++
When the Close button is selected, stop video playback and hide the lightbox.
Application styling
The CSS styles horizontal poster image scroller and the lightbox player.
Plugin code
Normally when converting the JavaScript into a Brightcove Player plugin nominal changes are needed. One required change is to replace the standard use of the ready()
method with the code that defines a plugin.
Here is the very commonly used start to JavaScript code that will work with the player:
videojs.getPlayer('myPlayerID').ready(function() {
var myPlayer = this;
...
});
You will change the first line to use the standard syntax to start a Brightcove Player plugin:
videojs.registerPlugin('pluginName', function(options) {
var myPlayer = this;
...
});
As mentioned earlier, you can see the plugin's JavaScript code in this document's corresponding GitHub repo: lightbox-scroller.js.
As mentioned earlier, you can see the plugin's JavaScript code in this document's corresponding GitHub repo: lightbox-scroller.js.
Using the plugin with a player
Once you have the plugin's CSS and JavaScript files stored in an Internet accessible location, you can use the plugin with a player. In Studio's PLAYERS module you can choose a player, then in the PLUGINS section add the URLs to the CSS and JavaScript files, and also add the Name and Options, if options are needed.