<html> <head> <title>Service TypeDetection</title> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> <link rel="stylesheet" type="text/css" href="../../../../idl.css"> </head> <body> <div id="adc-idlref"> <a name="_top_"> </a><table class="navimain" border="0" cellpadding="3"> <tr> <td class="navimain"><a href="../module-ix.html" class="navimain">Overview</a></td> <td class="navimain"><a href="module-ix.html" class="navimain">Module</a></td> <td class="navimain"><a href="TypeDetection-xref.html" class="navimain">Use</a></td> <td class="navimain"><a href="http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/OfficeDev/Integrating_Import_and_Export_Filters" class="navimain">Devguide</a></td> <td class="navimain"><a href="../../../../index-files/index-1.html" class="navimain">Index</a></td> </tr> </table> <table class="navisub" border="0" cellpadding="0"> <tr> <td class="navisub">Services' Summary</td> <td class="navisub"><a href="#InterfacesSummary" class="navisub">Interfaces' Summary</a></td> <td class="navisub">Properties' Summary</td> <td class="navisub">Services' Details</td> <td class="navisub"><a href="#InterfacesDetails" class="navisub">Interfaces' Details</a></td> <td class="navisub">Properties' Details</td> </tr> </table> <hr> <table border="0" width="100%" cellpadding="5" cellspacing="3" class="title-table" style="margin-bottom:6pt;"> <tr> <td><p class="namechain"><a href="../../../../module-ix.html" class="namechain">::</a> <a href="../../../module-ix.html" class="namechain">com</a> :: <a href="../../module-ix.html" class="namechain">sun</a> :: <a href="../module-ix.html" class="namechain">star</a> :: <a href="module-ix.html" class="namechain">document</a> :: </p> </td> </tr> <tr> <td class="title">service TypeDetection</td> </tr> <tr> <td><dl> <dt><b>Description</b></dt> <dd>encapsulate a type detection service and provide read/write access on it's configuration data. </dd> <dd><p> It's possible to make a "flat" detection which may use internal configuration data only - or a "deep" detection which use special <a href="ExtendedTypeDetection.html">ExtendedTypeDetection</a> services to look into the document stream. Last mode can be suppressed to perform the operation. Of course the results can't be guaranteed then. (e.g. in case the extension was changed) </p> </dd> </dl> <a name="devmanual"> </a><dl> <dt><b>Developers Guide</b></dt> <dd><a href="http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/OfficeDev/Integrating_Import_and_Export_Filters">OfficeDev - Integrating Import and Export Filters</a></dd> </dl> </td> </tr> </table> <hr> <a name="InterfacesSummary"/><table border="1" width="100%" cellpadding="5" cellspacing="0" class="subtitle"> <tr> <td class="subtitle" colspan="2">Exported Interfaces - Summary</td> </tr> <tr> <td class="imsum_left"><a href="XTypeDetection.html">XTypeDetection</a></td> <td class="imsum_right"><p>can be used to make a flat or deep type detection. (<a href="#XTypeDetection">details</a>)</p> </td> </tr> <tr> <td class="imsum_left">::com::sun::star::<a href="../container/module-ix.html">container</a>::<a href="../container/XNameAccess.html">XNameAccess</a></td> <td class="imsum_right"><p>provides read access to the complete set of type configuration data. (<a href="#XNameAccess">details</a>)</p> </td> </tr> <tr> <td class="imsum_left">::com::sun::star::<a href="../container/module-ix.html">container</a>::<a href="../container/XNameContainer.html">XNameContainer</a></td> <td class="imsum_right"><p>provides a write access to the configuration data. (<a href="#XNameContainer">details</a>)</p> </td> </tr> <tr> <td class="imsum_left">::com::sun::star::<a href="../container/module-ix.html">container</a>::<a href="../container/XContainerQuery.html">XContainerQuery</a></td> <td class="imsum_right"><p>provides search on the configuration data set. (<a href="#XContainerQuery">details</a>)</p> </td> </tr> <tr> <td class="imsum_left">::com::sun::star::<a href="../util/module-ix.html">util</a>::<a href="../util/XFlushable.html">XFlushable</a></td> <td class="imsum_right"><p>can be used to perform container changes. (<a href="#XFlushable">details</a>)</p> </td> </tr> </table> <a name="InterfacesDetails"/><table border="1" width="100%" cellpadding="5" cellspacing="0" class="subtitle"> <tr> <td class="subtitle" colspan="2">Exported Interfaces - Details</td> </tr> <tr/> <tr> <td class="imdetail"><a name="XTypeDetection" class="membertitle"><a href="XTypeDetection.html">XTypeDetection</a></a><table border="0" width="96%" cellpadding="5" cellspacing="0" class="table-in-data" bgcolor="#ffffff" align="center"> <tr> <td><dl> <dt><b>Description</b></dt> <dd>can be used to make a flat or deep type detection. </dd> <dd><p> Use this interface to get information about the type of the given resource. Return value will be always an internal name of a registered document type. It can be used may on other services (e.g. ::com::sun::star::<a href="../frame/module-ix.html">frame</a>::<a href="../frame/FrameLoaderFactory.html">FrameLoaderFactory</a>) to do further things, which base on it (e.g. to load it into a frame). </p> </dd> </dl> </td> </tr> </table> </td> </tr> <tr/> <tr> <td class="imdetail"><a name="XNameAccess" class="membertitle">::com::sun::star::<a href="../container/module-ix.html">container</a>::<a href="../container/XNameAccess.html">XNameAccess</a></a><table border="0" width="96%" cellpadding="5" cellspacing="0" class="table-in-data" bgcolor="#ffffff" align="center"> <tr> <td><dl> <dt><b>Description</b></dt> <dd>provides read access to the complete set of type configuration data. </dd> <dd><p> Every container item is specified as a set of properties and will be represented by a sequence< <type scope="com::sun::star::beans">PropertyValue > structure. Follow properties are supported: (But note: not all of them must be present every time!) <table border=1> <tr> <td><strong>Property Name</strong></td> <td><strong>Value Type</strong></td> <td><strong>Description</strong></td> </tr> <tr> <td><em>Name</em></td> <td>[string]</td> <td>The internal name is the only value, which makes a container item unique.</td> </tr> <tr> <td><em>UIName</em></td> <td>[string]</td> <td>It contains the localized name for this type for the current locale.</td> </tr> <tr> <td><em>UINames</em></td> <td>[sequence< string >]</td> <td>It contains all available localized names for this type. The are organized in pairs and represented as a structure of sequence< <type scope="com::sun::star::beans">PropertyValue >. The name of such property must be interpreted as locale; it's value as the localized type name corresponding to this locale.</td> </tr> <tr> <td><em>MediaType</em></td> <td>[string]</td> <td>It contains the MIME or content type descriptor. The differences between a MIME type and an internal type name was made, to resolve existing ambiguities.</td> </tr> <tr> <td><em>ClipboardFormat</em><strong>deprecated!</strong></td> <td>[string]</td> <td>It was interpreted as an identifier inside clipboard. Please use new property ContentFormat instead of this now.</td> </tr> <tr> <td><em>ContentFormat</em></td> <td>[string]</td> <td>It's and identifier, which is used for a deep format detection. An <a href="ExtendedTypeDetection.html">ExtendedTypeDetection</a> use this value to match a given content to this type. e.g. It's interpreted as the doc type of an XML stream or as an identifier inside a file header. </td> </tr> <tr> <td><em>URLPattern</em></td> <td>[sequence< string >]</td> <td>This list contains different URL patterns, which identify this type. E.g. data base contents can be described by an new defined protocol like "sql://select*". In combination with a suitable ::com::sun::star::<a href="../frame/module-ix.html">frame</a>::<a href="../frame/FrameLoader.html">FrameLoader</a> or <a href="ImportFilter.html">ImportFilter</a>/<a href="ExportFilter.html">ExportFilter</a> it would be possible then, to layout a SQL query output into an office frame.</td> </tr> <tr> <td><em>Extensions</em></td> <td>[sequence< string >]</td> <td>It contains a list of file extensions, which match this type. They must be specified as pure extension, without any special signs. E.g.: "doc", "html" ... but not ".doc". Using wild cards is allowed but not very useful. They may result in ambiguities with other type registrations can't be resolved anytime.</td> </tr> <tr> <td><em>DocumentIconID</em></td> <td>[integer]</td> <td>It's an ID, which present the number of a corresponding icon.</td> </tr> </table> </p> <p> Note:<br> All elements of this container will be addressed by his internal name, and it must be an unambiguous value. </p> </dd> </dl> </td> </tr> </table> </td> </tr> <tr/> <tr> <td class="imdetail"><a name="XNameContainer" class="membertitle">::com::sun::star::<a href="../container/module-ix.html">container</a>::<a href="../container/XNameContainer.html">XNameContainer</a></a><table border="0" width="96%" cellpadding="5" cellspacing="0" class="table-in-data" bgcolor="#ffffff" align="center"> <tr> <td><dl> <dt><b>Usage Restrictions</b></dt> <dd><i>optional</i></dd> <dt><b>Description</b></dt> <dd>provides a write access to the configuration data. </dd> </dl> </td> </tr> </table> </td> </tr> <tr/> <tr> <td class="imdetail"><a name="XContainerQuery" class="membertitle">::com::sun::star::<a href="../container/module-ix.html">container</a>::<a href="../container/XContainerQuery.html">XContainerQuery</a></a><table border="0" width="96%" cellpadding="5" cellspacing="0" class="table-in-data" bgcolor="#ffffff" align="center"> <tr> <td><dl> <dt><b>Usage Restrictions</b></dt> <dd><i>optional</i></dd> <dt><b>Description</b></dt> <dd>provides search on the configuration data set. </dd> <dd><p> Against simple property search it provides some complex algorithms too. For further informations please read the SDK documentation. </p> </dd> </dl> </td> </tr> </table> </td> </tr> <tr/> <tr> <td class="imdetail"><a name="XFlushable" class="membertitle">::com::sun::star::<a href="../util/module-ix.html">util</a>::<a href="../util/XFlushable.html">XFlushable</a></a><table border="0" width="96%" cellpadding="5" cellspacing="0" class="table-in-data" bgcolor="#ffffff" align="center"> <tr> <td><dl> <dt><b>Usage Restrictions</b></dt> <dd><i>optional</i></dd> <dt><b>Description</b></dt> <dd>can be used to perform container changes. </dd> <dd><p> Because the complexness of such configuration set can be very high, it seams not very useful to update the underlying configuration layer on every container change request immediately. Another strategy can be to make all changes (adding/changing/removing of items) and call flush at the end. That will validate the whole container and reject inconsistent data sets. Only in case all made changes was correct, they will be written back to the configuration. Further this interface provides the possibility, that interested changes listener can be registered too. </p> </dd> </dl> </td> </tr> </table> </td> </tr> </table> <br> <a href="#_top_">Top of Page</a><hr size="3"><p class="copyright" align="center">Copyright © 2000, 2012 LibreOffice contributors and/or their affiliates. All rights reserved.</p><p class="copyright" align="center">LibreOffice was created by The Document Foundation, based on OpenOffice.org, which is Copyright 2000, 2010 Oracle and/or its affiliates.</p><p class="copyright" align="center">The Document Foundation acknowledges all community members, please find more info <a href="http://www.libreoffice.org/about-us/credits/" target="_blank">at our website</a>.<p> </p><p class="copyright" align="center"><a href="http://www.libreoffice.org/privacy" target="_blank">Privacy Policy</a> | <a href="http://www.libreoffice.org/imprint" target="_blank">Impressum (Legal Info)</a> | Copyright information: The source code of LibreOffice is licensed under the GNU Lesser General Public License (<a href="http://www.libreoffice.org/download/license/" target="_blank">LGPLv3</a>). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our <a href="http://wiki.documentfoundation.org/TradeMark_Policy" target="_blank">trademark policy</a>.</p> </div> <!-- id="adc-idlref" --> </body> </html>
