Mountain View
Jabber SDK API Documentation

Tutorial: Video Windows And Video Rendering

Video Windows And Video Rendering

Title One of the main features of Jabber SDK is that video rendering is done from native application (Add-on). This leverages browser application from intensive CPU operations. CWIC library offers two type of video windows in which video rendering is performed, and that could be used in web applications:
  • In-browser video windows.
  • Native video windows.
Video window API is accessed through WindowController.

In-Browser Video Window

In-Browser Windows are supported only in browsers that support NPAPI (Safari, Firefox) or ActiveX Control (Internet Explorer) based plugins. These plugins allow creation of HTML objects in web applications in which video will be streamed directly into from native application (Add-on). Following topics will be covered:

Native Video Window

NativeVideoWindow are native windows in which video rendering is performed. These windows can be used from any browser that is supported by CWIC library, but have different capabilities depending on the browser and operating system. Since Chrome doesn't support NPAPI/ActiveX based plugins, in-browser video window cannot be used. NativeVideoWindow when used from Chrome has a support for docking. This means that native video window can be docked to targeted HTML element in web application, and thus act as an overlay window of targeted element and give an impression that window is rendered inside a web browser. In the following tutorials, following topics will be covered:

Next

Previous