How Cisco StadiumVision Mobile Fits into a Windows Phone Framework

This section provides background information as to how Cisco StadiumVision Mobile fits into a Windows Phone app. It contains the following sections:

Cisco StadiumVision Mobile Class Fundamentals

The SVMVideoPlayerPage class is a class within StadiumVisionMobile rather than an inherited class for the app's video page. A connection from the Windows Phone app to the SVMVideoPlayerPage class includes a reference to the "Windows DirectX SwapChainPanel" when the StadiumVisionMobile class is instantiated. StadiumVision Mobile Class describes the StadiumVision Mobile classes.

StadiumVision Mobile Class
 
Back to top of page

Windows Overview depicts the Windows OS with regard to Pages. A Page represents both the screen layout and controller code or Code Behind. A new Page is launched by sending an Event to the Windows OS. An Event is a message to Windows OS to launch a particular page. Extra parameters contained in an Event and are passed to a Page. The back button is typically a hard (sometimes soft) device button used to generically display the previous Page, and moves back down the Page stack.

Windows Overview
 
Back to top of page

Windows Video Player Window Inheritance depicts the Window inheritance between the Windows OS, Cisco StadiumVision Mobile, and the Customer App.

Windows Video Player Window Inheritance
 
Back to top of page

Cisco StadiumVision Mobile Integration Overview
 
Back to top of page

Customer Application Roles

Customer Application Responsibilities illustrates the roles of the customer application. The application must specify how to:

  • Get the list of video channels
  • Display the list of video channels
  • Handle user gestures for selecting video channels
  • Add video overlays and layouts
  • Handle user gestures to control video overlay
Customer Application Responsibilities