diff -r 4816d766a08a -r f345bda72bc4 Symbian3/PDK/Source/GUID-8BEE0411-C6E9-5840-BE22-EC271A4D97DD.dita --- a/Symbian3/PDK/Source/GUID-8BEE0411-C6E9-5840-BE22-EC271A4D97DD.dita Tue Mar 30 11:42:04 2010 +0100 +++ b/Symbian3/PDK/Source/GUID-8BEE0411-C6E9-5840-BE22-EC271A4D97DD.dita Tue Mar 30 11:56:28 2010 +0100 @@ -1,38 +1,38 @@ - - - - - -OpenWF -Composition Engine Component OverviewThe OpenWF Composition (OpenWF-C) Engine component consists of -a reference implementation of the OpenWF-C Interface. Device creators can -replace the Symbian platform implementation with their own. -

Target audience: Device creators.

-

The Symbian reference implementation is a pure software implementation -that is based on the Khronos sample OpenWF-C implementation, which was developed -by Ardites. The Symbian implementation has not been optimized for speed or -memory usage. Device creators can use all or part of the reference implementation -when they create their own implementations or they can replace it completely.

-

An OpenWF-C implementation must implement the public APIs defined by the OpenWF-C interface. -An OpenWF-C implementation can also implement extension functions. Clients -obtain extension functions by using eglGetProcAddress().

-

eglGetProcAddress() uses the first exported OpenWF-C -function to fill in a table of pointers to the OpenWF-C extension functions. -The OpenWF-C implementation must therefore export at ordinal position one -a function that provides pointers to all of the implemented extension functions.

-

In order to be able to claim that an OpenWF-C implementation conforms to -the Khronos standard, it must pass the relevant conformance tests. The OpenWF-C -conformance tests have been ported to Symbian and are available through the -Khronos website to those who have an appropriate license. However, you may -need to adapt the conformance test's porting layer further to make it work -with your implementation.

-
-OpenWF Composition - + + + + + +OpenWF +Composition Engine Component OverviewThe OpenWF Composition (OpenWF-C) Engine component consists of +a reference implementation of the OpenWF-C Interface. Device creators can +replace the Symbian platform implementation with their own. +

Target audience: Device creators.

+

The Symbian reference implementation is a pure software implementation +that is based on the Khronos sample OpenWF-C implementation, which was developed +by Ardites. The Symbian implementation has not been optimized for speed or +memory usage. Device creators can use all or part of the reference implementation +when they create their own implementations or they can replace it completely.

+

An OpenWF-C implementation must implement the public APIs defined by the OpenWF-C interface. +An OpenWF-C implementation can also implement extension functions. Clients +obtain extension functions by using eglGetProcAddress().

+

eglGetProcAddress() uses the first exported OpenWF-C +function to fill in a table of pointers to the OpenWF-C extension functions. +The OpenWF-C implementation must therefore export at ordinal position one +a function that provides pointers to all of the implemented extension functions.

+

In order to be able to claim that an OpenWF-C implementation conforms to +the Khronos standard, it must pass the relevant conformance tests. The OpenWF-C +conformance tests have been ported to Symbian and are available through the +Khronos website to those who have an appropriate license. However, you may +need to adapt the conformance test's porting layer further to make it work +with your implementation.

+
+OpenWF Composition +
\ No newline at end of file