diff -r 48780e181b38 -r 578be2adaf3e Symbian3/PDK/Source/GUID-89CFD892-16B0-5B70-AE46-D4BFB8412BC4.dita --- a/Symbian3/PDK/Source/GUID-89CFD892-16B0-5B70-AE46-D4BFB8412BC4.dita Tue Jul 20 12:00:49 2010 +0100 +++ b/Symbian3/PDK/Source/GUID-89CFD892-16B0-5B70-AE46-D4BFB8412BC4.dita Fri Aug 13 16:47:46 2010 +0100 @@ -1,83 +1,83 @@ - - - - - -OpenMAX -IL Content Pipe Interface Overview -

This document introduces you to the Symbian way of using OpenMAX IL Content -Pipe interface.

-
Purpose

The OpenMAX IL Content Pipe interface is -an ECom plug-in.

OpenMAX IL Content Pipe interface (entry point) is -provided as a static library, and the ECom implementation is defined as a -macro to allow OpenMAX IL Content Pipe to be built as an ECom plug-in with -very little overhead.

-
OpenMAX IL Content Pipe Interface library details

For -Symbian OpenMAX IL Content Pipe functionality you must adapt the following -static library file.

- - - -DLL -LIB -Short Description - - - - -

You must create your own *.dll

-

omxilsymbiancontentpipeif.lib

-

These files are used for implementing the OpenMAX IL Content Pipe -interface.

-
- - -
-
Architectural relationship

The OpenMAX IL Content -Pipe interface is accessed by OpenMAX IL Core as an ECom plugin, to pull the -content data in or to push the content data out from the source or destination. -For example, a local file, a remote file or a broadcast.

The OpenMAX -IL Content Pipe interface is implemented as an ECom plug-in in a similar approach -to the OpenMAX IL Component interface.

-
Description

The OpenMAX IL Content Pipe interface -implements the OpenMAX IL CP_PIPETYPE structure. The features -of the OpenMAX IL Content Pipe interface include functions for conventional -content manipulation to

    -
  • get the position from -the content using CP_PIPETYPE::GetPosition()

  • -
  • get a particular position -in the content using CP_PIPETYPE::SetPosition()

  • -
  • read data from the current -position using CP_PIPETYPE::read()

  • -
  • write data to the current -position using CP_PIPETYPE::Write()

  • -
  • allow some streaming -support by implementing OpenMAX IL Content Pipe's functions, such as CP_PIPETYPE::CheckAvailableBytes(), CP_PIPETYPE::ReadBuffer(), and CP_PIPETYPE::WriteBuffer().

  • -
-
Key classes of the OpenMAX IL Content Pipe interface

The -key classes of the OpenMAX IL Content Pipe interface are

    -
  • COmxILContentPipeIf, -which is an interface to connects the content pipes to load as an ECOM plugin.

  • -
  • COmxILSymbianContentPipeIf, -which is the symbian implementation of the OpenMAX IL Content Pipe interface -which defines the content pipe roles such as read or write access of data, -checks for valid memory size of data and arrange the data in the order it -is retrieved.

  • -
-
Using the OpenMAX IL Content Pipe interface

The -OpenMAX IL Content Pipe interface is used to provide content access by implementing -the data access abstraction interface define in the CP_PIPETYPE structure.

-
-OpenMAX IL -Core Overview -OpenMAX IL -Loader Interface Overview -OpenMAX IL -Component Overview + + + + + +OpenMAX +IL Content Pipe Interface Overview +

This document introduces you to the Symbian way of using OpenMAX IL Content +Pipe interface.

+
Purpose

The OpenMAX IL Content Pipe interface is +an ECom plug-in.

OpenMAX IL Content Pipe interface (entry point) is +provided as a static library, and the ECom implementation is defined as a +macro to allow OpenMAX IL Content Pipe to be built as an ECom plug-in with +very little overhead.

+
OpenMAX IL Content Pipe Interface library details

For +Symbian OpenMAX IL Content Pipe functionality you must adapt the following +static library file.

+ + + +DLL +LIB +Short Description + + + + +

You must create your own *.dll

+

omxilsymbiancontentpipeif.lib

+

These files are used for implementing the OpenMAX IL Content Pipe +interface.

+
+ + +
+
Architectural relationship

The OpenMAX IL Content +Pipe interface is accessed by OpenMAX IL Core as an ECom plugin, to pull the +content data in or to push the content data out from the source or destination. +For example, a local file, a remote file or a broadcast.

The OpenMAX +IL Content Pipe interface is implemented as an ECom plug-in in a similar approach +to the OpenMAX IL Component interface.

+
Description

The OpenMAX IL Content Pipe interface +implements the OpenMAX IL CP_PIPETYPE structure. The features +of the OpenMAX IL Content Pipe interface include functions for conventional +content manipulation to

    +
  • get the position from +the content using CP_PIPETYPE::GetPosition()

  • +
  • get a particular position +in the content using CP_PIPETYPE::SetPosition()

  • +
  • read data from the current +position using CP_PIPETYPE::read()

  • +
  • write data to the current +position using CP_PIPETYPE::Write()

  • +
  • allow some streaming +support by implementing OpenMAX IL Content Pipe's functions, such as CP_PIPETYPE::CheckAvailableBytes(), CP_PIPETYPE::ReadBuffer(), and CP_PIPETYPE::WriteBuffer().

  • +
+
Key classes of the OpenMAX IL Content Pipe interface

The +key classes of the OpenMAX IL Content Pipe interface are

    +
  • COmxILContentPipeIf, +which is an interface to connects the content pipes to load as an ECOM plugin.

  • +
  • COmxILSymbianContentPipeIf, +which is the symbian implementation of the OpenMAX IL Content Pipe interface +which defines the content pipe roles such as read or write access of data, +checks for valid memory size of data and arrange the data in the order it +is retrieved.

  • +
+
Using the OpenMAX IL Content Pipe interface

The +OpenMAX IL Content Pipe interface is used to provide content access by implementing +the data access abstraction interface define in the CP_PIPETYPE structure.

+
+OpenMAX IL +Core Overview +OpenMAX IL +Loader Interface Overview +OpenMAX IL +Component Overview
\ No newline at end of file