RiExerciser GUI

The GUI for the RiExerciser is based on a class hierarchy of Pages, with Page being the abstract superclass, and additional subclasses such as the QuarterPage class. Pages that include a user menu as well as a VideoTextBox should subclass QuarterPage. Being based essentially on a Model View Controller architecture, the OcapAppDriver is the Model class, the RiExerciserController is the Controller class, and the Pages along with RiExerciserContainer make up the View classes.

As the Controller, the RiExerciserController listens for KeyEvents. Some events are processed in RiExerciserController, such as changing channels, and stopping, pausing, or resuming playback. Most events are passed to the currently displayed Page, which processes the UserEvent.

Pages are essentially broken down into areas of functionality, such as DVR, Home Networking, or additional testing areas. The Pages are composed of menu options relating to the functional area of the Page. For example, the Recording Menu Page offers various options for making DVR recordings. Each Page contains the logic for executing user commands like publishing a recording to CDS, which typically involves calls to OcapAppDriver in order to make use of OCAP APIs.

The RiExerciserContainer class contains the user interface components that are common throughout the various menu Pages. This includes displaying messages relating to ServiceContextEvents and ControllerEvents, as well as messages related to the user requested operations such as making a recording. In addition, the RiExeriserContainer also includes displaying a status bar and progress bar for remote service and JMF playback.

The following diagram illustrates how user interaction is handled.

  • No labels