Client Views (Deprecated)
The client views provide sample code to implement a feature or features on a web page.
Where to Find the Code
The code sample includes multiple client web pages or views illustrating each feature and a seventh code sample that shows all the features working in combination. To implement this client page, you will need all the standard elements that you normally use to embed a player, such as your API Key, pcode, and so forth. For information about how to do this, you can check the API Keys and Partner Code documentation.To explore these code sample views in GitHub, go to: https://github.com/ooyala/code-samples/blob/master/application/views.
The following diagram shows the organization of all the views directory.
├── application (Main folder where the CodeIgniter application lives) ... │ └── views (Here we define all the views for the application.) │ │ ├── cross_resume.php │ │ └── google_ima.php │ │ ├── index.html │ │ └── message-bus-advanced.php │ │ ├── message-bus.php │ │ └── multi-feature.php │ │ └── simple.php │ │ ├── test.php │ │ └── token.php
You can review the corresponding server-side logic implemented in the controllers at https://github.com/ooyala/code-samples/blob/master/application/controllersThe client-side views or web pages are described in the following table:
|cross_resume.php||Contains the code with player_tokenauth - This file contains the code to implement the Ooyala Player.|
|google_ima.php||Contains the code to implement the Google IMA ad manager.|
|message-bus.php and||Illustrates the use of our message bus for event handling.|
|message-bus-advanced.php||Illustrates the use of our message bus for event handling.|
|multi-feature-sample.php||Contains the code that combines all of the features.|
|simple.php||Contains the simplest building block for using the Player. It contains the embed code for a running a single player on a web page.|
|token.php||Contains the code to implement Token Authentication for a single player on a web page.|
The following sections describe the implementation of each of these client-side views.