How Cisco StadiumVision Mobile Fits into the iOS Framework

Client Application Integration Components

Cisco StadiumVision Mobile iOS SDK Components illustrates the high-level view of the Cisco StadiumVision iOS API libraries and common framework components. The left side of the graphic represents how to modify the sample application, and the right represents how the SDK is packaged.

Back to top of page

iOS Model View Controller (MVC) Design Pattern

The Model View Controller (MVC) design pattern separates aspects of an application into three distinct parts and defines how the three communicate. MVC Design Pattern illustrates the Apple iOS MVC. As the name implies, the application is divided into three distinct parts: Model, View and Controller. The main purpose for MVC is reusability where you can reuse the same model for different views.

Back to top of page

Cisco StadiumVision Mobile iOS API Class Fundamentals

The singleton "StadiumVisionMobile" class provides the top-level API to start, configure, and stop the framework. "SVMVideoViewController" classes are provided to play the video channels and to allow for customization. Cisco StadiumVision Mobile iOS API Classes illustrates the Cisco StadiumVision Mobile API classes.

Back to top of page

Video View Controller Inheritance

The iOS "UIViewController" and "UIView" classes are used as base classes. The customer application can extend the Cisco StadiumVision Mobile classes. Cisco StadiumVision Mobile Video Classes illustrates the UIViewController and UIView classes.

Back to top of page

Cisco StadiumVision Mobile Application Classes

The Cisco StadiumVision Mobile application classes:

• Extend and customize the SVMVideoViewController class.
• Add a UI overlay for controlling video playback (play, stop, close).
• Add a UI overlay for displaying Cisco StadiumVision Mobile stats.
• Handle gestures to display UI overlays with the MyVideoViewController class.