How Cisco StadiumVision Mobile Fits into the Android Framework
This section provides background information as to how Cisco StadiumVision Mobile fits into an Android Phone app. It contains the following sections:
- Android API Class Fundamentals
- Android OS Activities
- Client Application Integration
- Customer Application Roles
Android API Class Fundamentals
StadiumVision Mobile Class describes the three main Android API classes used in Cisco StadiumVision Mobile. The top-level StadiumVisionMobile class acts as a custom Android application context. An application context is a global structure created within the current process. It is tied to the lifetime of the process rather than the current component.
Each SDK API method is called using the StadiumVisionMobile class. The SVMVideoPlayerActivity class is a customizable stand-alone video player.
Android OS Activities
Android Activities depicts the Android OS with regard to Activities. An Activity represents both the screen layout and controller code. A new Activity is launched by sending an Intent to the Android OS. An intent is a message to Android OS to launch a particular activity. Extra parameters contained in an Intent and are passed to an Activity. The back button is a hard device button used to generically display the previous Activity, and moves back down the Activity stack.
Android Video Player Activity Inheritance depicts the Activity inheritance between the Android OS, Cisco StadiumVision Mobile, and the client application.
Customer Application Roles
Customer Application Responsibilities illustrates the roles of the customer application. The application must specify how to:
