Difference between revisions of "Documentation/DevGuide/OfficeDev/Document API Filter Development"

From Apache OpenOffice Wiki
Jump to: navigation, search
m (Robot: Changing Category:Documentation/Developers Guide/Office Development)
 
(7 intermediate revisions by 2 users not shown)
Line 4: Line 4:
 
|OfficeDevDocFilter=block
 
|OfficeDevDocFilter=block
 
|ShowPrevNext=block
 
|ShowPrevNext=block
|PrevPage=Documentation/DevGuide/OfficeDev/Integrating Import and Export Filters
+
|PrevPage=Documentation/DevGuide/OfficeDev/Properties of a FrameLoader
|NextPage=Documentation/DevGuide/OfficeDev/Filtering Process
+
|NextPage=Documentation/DevGuide/OfficeDev/XML_Based_Filter_Development
 
}}
 
}}
{{DISPLAYTITLE:Document API Filter Development}}
+
{{Documentation/DevGuideLanguages|Documentation/DevGuide/OfficeDev/{{SUBPAGENAME}}}}
First, we provide an overview of the import and export process using a document API, and gain an understanding of the general concepts.
+
{{DISPLAYTITLE:Document API Filter Development}}
  
=== Introduction ===
+
TBD: Examples.
 
+
Inside {{PRODUCTNAME}} a document is represented by its document service, called model. On disk, the same document is represented as a file or possibly as a dynamic generated output, for example, of a database statement. We cannot assign it to a file on disk, so we call it content to describe it. A filter component is used to convert between these different formats.
+
 
+
[[Image:import_export.png|none|thumb|300px|Import/Export Filter Process]]
+
 
+
If you make use of UNO, this above diagram can be turned into programming reality quite easily. The three entities in the diagram, content, model, and filter, all have direct counterparts in UNO services. The services consist of several interfaces that map to a specific implementation, for example, using C++ or Java.
+
 
+
The filter writer creates a class that implements the <idl>com.sun.star.document.ExportFilter</idl> or <idl>com.sun.star.document.ImportFilter</idl> services, or both. To achieve this, the corresponding stream or URL is obtained from the <idl>com.sun.star.document.MediaDescriptor</idl>. The incoming data is then interpreted and the model is used by calling the appropriate methods. The available methods depend on the type of document as described by the document service.
+
 
+
For a list of available document services, refer to the section [[Documentation/DevGuide/OfficeDev/Component/Models#Document Specific Features|Document Specific Features]].
+
  
 
{{PDL1}}
 
{{PDL1}}
  
 
[[Category:Documentation/Developer's Guide/Office Development]]
 
[[Category:Documentation/Developer's Guide/Office Development]]

Latest revision as of 08:10, 14 May 2009



TBD: Examples.

Content on this page is licensed under the Public Documentation License (PDL).
Personal tools
In other languages