Sophie

Sophie

distrib > Fedora > 13 > i386 > by-pkgid > d4407d1b28dc9463b6e6d9d6c9fc666a > files > 14

oyranos-devel-0.1.9-4.fc12.i686.rpm

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head><meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
<title>Oyranos: Data Structures</title>
<link href="tabs.css" rel="stylesheet" type="text/css">
<link href="doxygen.css" rel="stylesheet" type="text/css">
</head><body>
<!-- Generated by Doxygen 1.5.9 -->
<div class="navigation" id="top">
  <div class="tabs">
    <ul>
      <li><a href="index.html"><span>Main&nbsp;Page</span></a></li>
      <li><a href="pages.html"><span>Related&nbsp;Pages</span></a></li>
      <li><a href="modules.html"><span>Modules</span></a></li>
      <li><a href="namespaces.html"><span>Namespaces</span></a></li>
      <li class="current"><a href="annotated.html"><span>Data&nbsp;Structures</span></a></li>
      <li><a href="files.html"><span>Files</span></a></li>
    </ul>
  </div>
  <div class="tabs">
    <ul>
      <li class="current"><a href="annotated.html"><span>Data&nbsp;Structures</span></a></li>
      <li><a href="classes.html"><span>Data&nbsp;Structure&nbsp;Index</span></a></li>
      <li><a href="functions.html"><span>Data&nbsp;Fields</span></a></li>
    </ul>
  </div>
</div>
<div class="contents">
<h1>Data Structures</h1>Here are the data structures with brief descriptions:<table>
  <tr><td class="indexkey"><a class="el" href="structoyArray2d__s.html">oyArray2d_s</a></td><td class="indexvalue">2d data array<p>
<a class="el" href="structoyArray2d__s.html" title="2d data arrayoyArray2d_s is a in memory data view. The array2d holds pointers to...">oyArray2d_s</a> is a in memory data view. The array2d holds pointers to lines in the original memory blob. The arrays contained in array2d represent the samples. There is no information in which order the samples appear. No pixel layout or meaning is provided. Given the coordinates x and y, a samples memory adress can be accessed by &amp;array2d[y][x] . This adress must be converted to the data type provided in <a class="el" href="structoyArray2d__s.html#fd7beac4067abc61dd2f9cde51de01d3">oyArray2d_s::t</a> </td></tr>
  <tr><td class="indexkey"><a class="el" href="structoyCMMInfo__s.html">oyCMMInfo_s</a></td><td class="indexvalue">CMM API resources struct to implement and set by a CMM<p>
Given an example CMM with name "little cms", which wants to use the four-char ID 'lcms', the CMM can register itself to Oyranos as follows: The CMM module file must be named something_lcms_cmm_module_something.something . On Linux this could be "liboyranos_lcms_cmm_module.so.0.1.8". The four-chars 'lcms' must be prepended with OY_MODULE_NAME alias "_cmm_module" </td></tr>
  <tr><td class="indexkey"><a class="el" href="structoyColourConversion__s.html">oyColourConversion_s</a></td><td class="indexvalue"></td></tr>
  <tr><td class="indexkey"><a class="el" href="structoyConnector__s.html">oyConnector_s</a></td><td class="indexvalue">Filter connection description structure<p>
This structure holds informations about the connection capabilities. It holds common structure members of <a class="el" href="structoyFilterPlug__s.html" title="a filter connection structureThe active input version of a oyConnector_s. Each plug...">oyFilterPlug_s</a> and <a class="el" href="structoyFilterSocket__s.html" title="a filter connection structureThe passive output version of a oyConnector_s.">oyFilterSocket_s</a> </td></tr>
  <tr><td class="indexkey"><a class="el" href="structoyConversion__s.html">oyConversion_s</a></td><td class="indexvalue">Filter chain or graph to manipulate a image<p>
Order of filters matters. The processing direction is a bit like raytracing as nodes request their parent </td></tr>
  <tr><td class="indexkey"><a class="el" href="structoyFilter__s.html">oyFilter_s</a></td><td class="indexvalue">Filter to manipulate a image<p>
This is the Oyranos filter object. Filters are categorised into basic classes of filters described in the filter_type_ member. Filters implement a container for data and options. Filters can be manipulated by changing their options or data set </td></tr>
  <tr><td class="indexkey"><a class="el" href="structoyFilterNode__s.html">oyFilterNode_s</a></td><td class="indexvalue">FilterNode object<p>
Filter nodes chain filters into a <a class="el" href="structoyConversion__s.html" title="a filter chain or graph to manipulate a imageOrder of filters matters. The processing...">oyConversion_s</a> graph. The filter nodes use plugs and sockets for creating connections. Each plug can only connect to one socket </td></tr>
  <tr><td class="indexkey"><a class="el" href="structoyFilterPlug__s.html">oyFilterPlug_s</a></td><td class="indexvalue">Filter connection structure<p>
The active input version of a <a class="el" href="structoyConnector__s.html" title="a filter connection description structureThis structure holds informations about...">oyConnector_s</a>. Each plug can connect to exact one socket </td></tr>
  <tr><td class="indexkey"><a class="el" href="structoyFilterPlugs__s.html">oyFilterPlugs_s</a></td><td class="indexvalue">FilterPlugs list </td></tr>
  <tr><td class="indexkey"><a class="el" href="structoyFilters__s.html">oyFilters_s</a></td><td class="indexvalue">Filters list </td></tr>
  <tr><td class="indexkey"><a class="el" href="structoyFilterSocket__s.html">oyFilterSocket_s</a></td><td class="indexvalue">Filter connection structure<p>
The passive output version of a <a class="el" href="structoyConnector__s.html" title="a filter connection description structureThis structure holds informations about...">oyConnector_s</a> </td></tr>
  <tr><td class="indexkey"><a class="el" href="structoyIcon__s.html">oyIcon_s</a></td><td class="indexvalue">Icon data<p>
Since: 0.1.8 </td></tr>
  <tr><td class="indexkey"><a class="el" href="structoyImage__s.html">oyImage_s</a></td><td class="indexvalue">Reference struct to gather information for image transformation<p>
as we dont target a complete imaging solution, only raster is supported </td></tr>
  <tr><td class="indexkey"><a class="el" href="structoyName__s.html">oyName_s</a></td><td class="indexvalue">Oyranos name structure </td></tr>
  <tr><td class="indexkey"><a class="el" href="structoyNamedColour__s.html">oyNamedColour_s</a></td><td class="indexvalue">Colour patch with meta informations<p>
Data management on library side. User can control memory management at creation time </td></tr>
  <tr><td class="indexkey"><a class="el" href="structoyNamedColours__s.html">oyNamedColours_s</a></td><td class="indexvalue">List of colour patches<p>
Data management on library side. User can control memory management at creation time </td></tr>
  <tr><td class="indexkey"><a class="el" href="structoyObject__s.html">oyObject_s</a></td><td class="indexvalue">Oyranos structure base<p>
The base object of Oyranos object system is self contained. It can be handled by the belonging function set. Complex objects for user interaction should almost all be derived from this struct.<br>
 The memory management can be controlled by the user and will affect internal and derived data </td></tr>
  <tr><td class="indexkey"><a class="el" href="structoyOption__s.html">oyOption_s</a></td><td class="indexvalue">Option for rendering </td></tr>
  <tr><td class="indexkey"><a class="el" href="structoyOptions__s.html">oyOptions_s</a></td><td class="indexvalue">Generic Options<p>
Options can be any flag or rendering intent and other informations needed to configure a process. The object contains a list of <a class="el" href="structoyOption__s.html" title="Option for rendering.">oyOption_s</a> objects </td></tr>
  <tr><td class="indexkey"><a class="el" href="structoyPixelAccess__s.html">oyPixelAccess_s</a></td><td class="indexvalue">Control pixel access order<p>
A struct to control pixel access. It is a kind of flexible pixel iterator. The order or pattern of access is defined by the array_xy and start_[x,y] variables </td></tr>
  <tr><td class="indexkey"><a class="el" href="structoyProfile__s.html">oyProfile_s</a></td><td class="indexvalue">Profile and its attributes </td></tr>
  <tr><td class="indexkey"><a class="el" href="structoyProfiles__s.html">oyProfiles_s</a></td><td class="indexvalue">Tell about the conversion profiles </td></tr>
  <tr><td class="indexkey"><a class="el" href="structoyProfileTag__s.html">oyProfileTag_s</a></td><td class="indexvalue">Profile constituting element </td></tr>
  <tr><td class="indexkey"><a class="el" href="structoyRegion__s.html">oyRegion_s</a></td><td class="indexvalue">Start with a simple rectangle </td></tr>
  <tr><td class="indexkey"><a class="el" href="structoyStruct__s.html">oyStruct_s</a></td><td class="indexvalue">Oyranos base structure<p>
All Oyranos structures should be castable to this basic one </td></tr>
  <tr><td class="indexkey"><a class="el" href="unionoyValue__u.html">oyValue_u</a></td><td class="indexvalue">Value </td></tr>
</table>
</div>
<hr size="1"><address style="text-align: right;"><small>Generated on Mon Jul 27 04:18:00 2009 for Oyranos by&nbsp;
<a href="http://www.doxygen.org/index.html">
<img src="doxygen.png" alt="doxygen" align="middle" border="0"></a> 1.5.9 </small></address>
</body>
</html>