diff -r 51a74ef9ed63 -r ae94777fff8f Symbian3/SDK/Source/GUID-46121F24-AB53-5B44-A082-EF13A72EB7FF.dita --- a/Symbian3/SDK/Source/GUID-46121F24-AB53-5B44-A082-EF13A72EB7FF.dita Wed Mar 31 11:11:55 2010 +0100 +++ b/Symbian3/SDK/Source/GUID-46121F24-AB53-5B44-A082-EF13A72EB7FF.dita Fri Jun 11 12:39:03 2010 +0100 @@ -1,52 +1,52 @@ - - - - - -Writing -a ConverterFile Converter Framework specifies a plug-in interface for file -format converters. Clients can convert from one data type to another using -file format converters, for example, HTML files to Word documents. - -
Introduction

The File Converter Framework provides -the following:

    -

  • An abstract interface -which all converters must implement.

    • -

  • APIs to list and search -for converters.

    • -

  • APIs to determine the -MIME types supported by the available converters.

    • -

  • An observer interface -through which the progress and success or failure of the conversion can be -reported.

    • -

Converters are implemented as ECom -plug-ins, each of which can implement one or more converters. Like -all binaries, the plug-ins are installed in the \sys\bin\ directory. -Each plug-in must provide two resource files: one contains a CONARC_RESOURCE_FILE resource -to describe the converters implemented in the DLL, and the other is a registration -resource file required by the ECom framework.

The following UML diagram -shows the key elements of the converter architecture, including an example -client and an example converter DLL that provides two converters, myConverter1 and myConverter2.

- File Converter architecture - -
-
Procedure
    -

  1. Write -an interface implementation for a converter.

    2. -

  2. Implement -the ECom framework code.

    3. -

  3. Write -a resource file.

    4. -

  4. Write -a converter DLL project file.

    5. -
- -File Converter -Framework Overview + + + + + +Writing +a ConverterFile Converter Framework specifies a plug-in interface for file +format converters. Clients can convert from one data type to another using +file format converters, for example, HTML files to Word documents. + +
Introduction

The File Converter Framework provides +the following:

    +

  • An abstract interface +which all converters must implement.

    • +

  • APIs to list and search +for converters.

    • +

  • APIs to determine the +MIME types supported by the available converters.

    • +

  • An observer interface +through which the progress and success or failure of the conversion can be +reported.

    • +

Converters are implemented as ECom +plug-ins, each of which can implement one or more converters. Like +all binaries, the plug-ins are installed in the \sys\bin\ directory. +Each plug-in must provide two resource files: one contains a CONARC_RESOURCE_FILE resource +to describe the converters implemented in the DLL, and the other is a registration +resource file required by the ECom framework.

The following UML diagram +shows the key elements of the converter architecture, including an example +client and an example converter DLL that provides two converters, myConverter1 and myConverter2.

+ File Converter architecture + +
+
Procedure
    +

  1. Write +an interface implementation for a converter.

    2. +

  2. Implement +the ECom framework code.

    3. +

  3. Write +a resource file.

    4. +

  4. Write +a converter DLL project file.

    5. +
+ +File Converter +Framework Overview \ No newline at end of file