When you click on the buttons above the player, different playlists will load into the player.
View the source code.
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.
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)
- 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 Quick Start: 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:
- 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
API/Plugin resources used
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.
No special configuration is required for the Brightcove Player you create for this sample.
Of course, the three buttons are added to the page. Also, the
<ol> that determines the position of the playlist is also added.
The basic logic behind this application is:
- Listen for the click events from the buttons.
- When a button is clicked, use the Video Cloud catalog to retrieve the playlist and load it into the player.
- Use the Playlist API to play the first video in the playlist.
Add buttons with click events to call the
Find the code which is labeled:
<!-- +++ Add buttons for playlist selection +++ -->
onclick event handler the playlist to play is hard coded.
Load the playlist and play the first video
Find the code which is labeled:
// ### Retrieve and load playlist ###
load() methods retrieve the playlist and place it in the player. Lastly, the Playlist API's
first() method then plays the video.
The CSS sizes and positions the player and playlist.
postMessage method to pass the button clicked event to a plugin, the much more common use case is to just use the in-page embed player, so no plugin code is used.