ColourWiki - Recent changes [en]

ColourWiki - Recent changes [en] 2007-12-19T19:28:36Z Track the most recent changes to the wiki on this page. MediaWiki 1.4.10 CMM API 2007-12-19T14:10:29Z 2007-12-19T14:10:29 2007-12-19T14:10:29Z

/* Pixel Layout */ <table border='0' width='98%' cellpadding='0' cellspacing='4' class='diff'> <tr> <td colspan='2' width='50%' align='center' class='diff-otitle'>Revision as of 14:10, 19 Dec 2007</td> <td colspan='2' width='50%' align='center' class='diff-ntitle'>Current revision</td> </tr> <tr><td colspan="2" align="left">Line 112:</td> <td colspan="2" align="left">Line 112:</td></tr> <tr><td> </td><td class='diff-context'> oyDOUBLE /*!< IEEE double precission floating point number */</td><td> </td><td class='diff-context'> oyDOUBLE /*!< IEEE double precission floating point number */</td></tr> <tr><td> </td><td class='diff-context'> } oyDATATYPE_e;</td><td> </td><td class='diff-context'> } oyDATATYPE_e;</td></tr> <tr><td>-</td><td class='diff-deletedline'> </td><td>+</td><td class='diff-addedline'> </td></tr> <tr><td>-</td><td class='diff-deletedline'> /** parametric enum as shorthand for the channel layout in bitmaps</td><td>+</td><td class='diff-addedline'>The below pixel description is slightly different from lcms layout as it relies on the addtional </td></tr> <tr><td colspan="2"> </td><td>+</td><td class='diff-addedline'>profile information, to avoid concurrent definitions for the colour channels.</td></tr> <tr><td colspan="2"> </td><td>+</td><td class='diff-addedline'> </td></tr> <tr><td colspan="2"> </td><td>+</td><td class='diff-addedline'> /** @type oyPixel_t parametric uint32_t integer as shorthand for the channel layout in bitmaps</td></tr> <tr><td> </td><td class='diff-context'> </td><td> </td><td class='diff-context'> </td></tr> <tr><td> </td><td class='diff-context'> should fit into a 32bit type, usual unsigned int or uint32_t</td><td> </td><td class='diff-context'> should fit into a 32bit type, usual unsigned int or uint32_t</td></tr> <tr><td colspan="2" align="left">Line 129:</td> <td colspan="2" align="left">Line 132:</td></tr> <tr><td> </td><td class='diff-context'> </td><td> </td><td class='diff-context'> </td></tr> <tr><td> </td><td class='diff-context'> */</td><td> </td><td class='diff-context'> */</td></tr> <tr><td>-</td><td class='diff-deletedline'></td><td colspan="2"> </td></tr> <tr><td>-</td><td class='diff-deletedline'>The above pixel description is slightly different from lcms layout as it relies on the addtional </td><td colspan="2"> </td></tr> <tr><td>-</td><td class='diff-deletedline'>profile information, to avoid concurrent definitions for the colour channels.</td><td colspan="2"> </td></tr> <tr><td> </td><td class='diff-context'></td><td> </td><td class='diff-context'></td></tr> <tr><td> </td><td class='diff-context'> /** @brief CMM capability query enum</td><td> </td><td class='diff-context'> /** @brief CMM capability query enum</td></tr> <tr><td colspan="2" align="left">Line 229:</td> <td colspan="2" align="left">Line 229:</td></tr> <tr><td> </td><td class='diff-context'> } oyCMMapi1_s;</td><td> </td><td class='diff-context'> } oyCMMapi1_s;</td></tr> <tr><td> </td><td class='diff-context'></td><td> </td><td class='diff-context'></td></tr> <tr><td>-</td><td class='diff-deletedline'> </td><td colspan="2"> </td></tr> <tr><td> </td><td class='diff-context'>=== Discussion ===</td><td> </td><td class='diff-context'>=== Discussion ===</td></tr> <tr><td> </td><td class='diff-context'></td><td> </td><td class='diff-context'></td></tr> </table>

KaiUweBehrmann foobar OpenIccDirectoryProposal 2007-12-19T11:33:16Z 2007-12-19T11:33:16 2007-12-19T11:33:16Z

<table border='0' width='98%' cellpadding='0' cellspacing='4' class='diff'> <tr> <td colspan='2' width='50%' align='center' class='diff-otitle'>Revision as of 11:33, 19 Dec 2007</td> <td colspan='2' width='50%' align='center' class='diff-ntitle'>Current revision</td> </tr> <tr><td colspan="2" align="left">Line 123:</td> <td colspan="2" align="left">Line 123:</td></tr> <tr><td> </td><td class='diff-context'>'''''settings'''''/</td><td> </td><td class='diff-context'>'''''settings'''''/</td></tr> <tr><td> </td><td class='diff-context'></td><td> </td><td class='diff-context'></td></tr> <tr><td>-</td><td class='diff-deletedline'>Binary blobs should be preferedly go into the _DATA_ and clear text ones the _CONFIG_ route.</td><td>+</td><td class='diff-addedline'>Binary blobs should be preferedly go the _DATA_ and clear text ones the _CONFIG_ route.</td></tr> <tr><td> </td><td class='diff-context'></td><td> </td><td class='diff-context'></td></tr> <tr><td> </td><td class='diff-context'>== CMMs ==</td><td> </td><td class='diff-context'>== CMMs ==</td></tr> <tr><td>-</td><td class='diff-deletedline'>CMM's register can be stored in:</td><td>+</td><td class='diff-addedline'>CMM's register files can be stored in:</td></tr> <tr><td> </td><td class='diff-context'></td><td> </td><td class='diff-context'></td></tr> <tr><td> </td><td class='diff-context'>'''''cmms'''''/</td><td> </td><td class='diff-context'>'''''cmms'''''/</td></tr> <tr><td> </td><td class='diff-context'></td><td> </td><td class='diff-context'></td></tr> <tr><td>-</td><td class='diff-deletedline'>Binary blobs should be preferedly go into the _DATA_ and clear text ones the _CONFIG_ route.</td><td>+</td><td class='diff-addedline'>Binary blobs should be preferedly go the _DATA_ and clear text ones the _CONFIG_ route.</td></tr> <tr><td> </td><td class='diff-context'></td><td> </td><td class='diff-context'></td></tr> <tr><td> </td><td class='diff-context'>== Installation ==</td><td> </td><td class='diff-context'>== Installation ==</td></tr> </table>

Oyadmin foobar Talk:OpenIccDirectoryProposal 2007-12-19T11:32:17Z 2007-12-19T11:32:17 2007-12-19T11:32:17Z

KaiUweBehrmann foobar OpenIccDirectoryProposal 2007-12-19T11:29:34Z 2007-12-19T11:29:34 2007-12-19T11:29:34Z

coexisting XDG and CMS paths, add XDG_CONFIG_PATH, Installation <table border='0' width='98%' cellpadding='0' cellspacing='4' class='diff'> <tr> <td colspan='2' width='50%' align='center' class='diff-otitle'>Revision as of 11:29, 19 Dec 2007</td> <td colspan='2' width='50%' align='center' class='diff-ntitle'>Current revision</td> </tr> <tr><td colspan="2" align="left">Line 28:</td> <td colspan="2" align="left">Line 28:</td></tr> <tr><td> </td><td class='diff-context'>| Kai-Uwe Behrmann</td><td> </td><td class='diff-context'>| Kai-Uwe Behrmann</td></tr> <tr><td> </td><td class='diff-context'>| slightly modified formulations</td><td> </td><td class='diff-context'>| slightly modified formulations</td></tr> <tr><td colspan="2"> </td><td>+</td><td class='diff-addedline'>|-</td></tr> <tr><td colspan="2"> </td><td>+</td><td class='diff-addedline'>| Revision 0.1.5</td></tr> <tr><td colspan="2"> </td><td>+</td><td class='diff-addedline'>| 2007-12-19</td></tr> <tr><td colspan="2"> </td><td>+</td><td class='diff-addedline'>| Kai-Uwe Behrmann</td></tr> <tr><td colspan="2"> </td><td>+</td><td class='diff-addedline'>| coexisting XDG and CMS paths, add XDG_CONFIG_PATH, Installation</td></tr> <tr><td> </td><td class='diff-context'>|-</td><td> </td><td class='diff-context'>|-</td></tr> <tr><td> </td><td class='diff-context'>|}</td><td> </td><td class='diff-context'>|}</td></tr> <tr><td colspan="2" align="left">Line 49:</td> <td colspan="2" align="left">Line 54:</td></tr> <tr><td> </td><td class='diff-context'></td><td> </td><td class='diff-context'></td></tr> <tr><td> </td><td class='diff-context'>'''''$XDG_CONFIG_HOME/color'''''</td><td> </td><td class='diff-context'>'''''$XDG_CONFIG_HOME/color'''''</td></tr> <tr><td>-</td><td class='diff-deletedline'>or if XDG_CONFIG_HOME is not set, alternatively</td><td>+</td><td class='diff-addedline'>and</td></tr> <tr><td> </td><td class='diff-context'></td><td> </td><td class='diff-context'></td></tr> <tr><td> </td><td class='diff-context'>'''''$HOME/.config/color'''''</td><td> </td><td class='diff-context'>'''''$HOME/.config/color'''''</td></tr> <tr><td>-</td><td class='diff-deletedline'>for a top directory to store configuration files in its subdirectories.</td><td>+</td><td class='diff-addedline'>for a top directory to store human readable configuration files in its subdirectories.</td></tr> <tr><td> </td><td class='diff-context'></td><td> </td><td class='diff-context'></td></tr> <tr><td> </td><td class='diff-context'></td><td> </td><td class='diff-context'></td></tr> <tr><td> </td><td class='diff-context'>'''''$XDG_DATA_HOME/color'''''</td><td> </td><td class='diff-context'>'''''$XDG_DATA_HOME/color'''''</td></tr> <tr><td>-</td><td class='diff-deletedline'>or, if XDG_DATA_HOME is not set, alternatively</td><td>+</td><td class='diff-addedline'>and</td></tr> <tr><td> </td><td class='diff-context'></td><td> </td><td class='diff-context'></td></tr> <tr><td> </td><td class='diff-context'>'''''$HOME/.local/share/color'''''</td><td> </td><td class='diff-context'>'''''$HOME/.local/share/color'''''</td></tr> <tr><td colspan="2" align="left">Line 67:</td> <td colspan="2" align="left">Line 72:</td></tr> <tr><td> </td><td class='diff-context'></td><td> </td><td class='diff-context'></td></tr> <tr><td> </td><td class='diff-context'></td><td> </td><td class='diff-context'></td></tr> <tr><td>-</td><td class='diff-deletedline'>As system wide installation paths exist the XDG_DATA_DIRS variable, which itself can contain several directory entries:</td><td>+</td><td class='diff-addedline'>As system wide installation paths exist the '''''XDG_DATA_DIRS''''' and '''''XDG_CONFIG_DIRS''''' variables, which itself can contain several directory entries:</td></tr> <tr><td> </td><td class='diff-context'></td><td> </td><td class='diff-context'></td></tr> <tr><td>-</td><td class='diff-deletedline'>'''''$XDG_DATA_DIRS'''''[0]'''''/color''''', '''''$XDG_DATA_DIRS'''''[1]'''''/color''''' and so on, or alternatively</td><td>+</td><td class='diff-addedline'>'''''$XDG_DATA_DIRS'''''[0]'''''/color''''', '''''$XDG_DATA_DIRS'''''[1]'''''/color''''' and so on, plus</td></tr> <tr><td> </td><td class='diff-context'></td><td> </td><td class='diff-context'></td></tr> <tr><td>-</td><td class='diff-deletedline'>two system paths, due to different system directory layouts, exist and should be searched for:</td><td>+</td><td class='diff-addedline'>two system paths, due to different system directory layouts, exist and should always be searched for:</td></tr> <tr><td> </td><td class='diff-context'></td><td> </td><td class='diff-context'></td></tr> <tr><td> </td><td class='diff-context'>'''''/usr/local/share/color'''''</td><td> </td><td class='diff-context'>'''''/usr/local/share/color'''''</td></tr> <tr><td colspan="2" align="left">Line 78:</td> <td colspan="2" align="left">Line 83:</td></tr> <tr><td> </td><td class='diff-context'></td><td> </td><td class='diff-context'></td></tr> <tr><td> </td><td class='diff-context'>'''''/usr/share/color''''' as typical for Linux packages.</td><td> </td><td class='diff-context'>'''''/usr/share/color''''' as typical for Linux packages.</td></tr> <tr><td>-</td><td class='diff-deletedline'></td><td colspan="2"> </td></tr> <tr><td>-</td><td class='diff-deletedline'>An application path points to:</td><td colspan="2"> </td></tr> <tr><td>-</td><td class='diff-deletedline'></td><td colspan="2"> </td></tr> <tr><td>-</td><td class='diff-deletedline'>'''''$PREFIX/share/color'''''</td><td colspan="2"> </td></tr> <tr><td> </td><td class='diff-context'></td><td> </td><td class='diff-context'></td></tr> <tr><td> </td><td class='diff-context'>These above paths are considered top level entry points and should contain almost no files.</td><td> </td><td class='diff-context'>These above paths are considered top level entry points and should contain almost no files.</td></tr> <tr><td colspan="2" align="left">Line 87:</td> <td colspan="2" align="left">Line 88:</td></tr> <tr><td> </td><td class='diff-context'></td><td> </td><td class='diff-context'></td></tr> <tr><td> </td><td class='diff-context'>Typical colour configuration data is architecture independent. The configuration can therefore stay in one place as further described below.</td><td> </td><td class='diff-context'>Typical colour configuration data is architecture independent. The configuration can therefore stay in one place as further described below.</td></tr> <tr><td>-</td><td class='diff-deletedline'>Architecture dependent CMM modules and utilities should go into the usual file system places for libraries and binary executables.</td><td>+</td><td class='diff-addedline'>Architecture dependent CMM modules and utilities should reside below the usual system paths for libraries and binary executables. They are here not described in detail.</td></tr> <tr><td> </td><td class='diff-context'></td><td> </td><td class='diff-context'></td></tr> <tr><td> </td><td class='diff-context'>== Colour Profile Paths ==</td><td> </td><td class='diff-context'>== Colour Profile Paths ==</td></tr> <tr><td colspan="2" align="left">Line 122:</td> <td colspan="2" align="left">Line 123:</td></tr> <tr><td> </td><td class='diff-context'>'''''settings'''''/</td><td> </td><td class='diff-context'>'''''settings'''''/</td></tr> <tr><td> </td><td class='diff-context'></td><td> </td><td class='diff-context'></td></tr> <tr><td colspan="2"> </td><td>+</td><td class='diff-addedline'>Binary blobs should be preferedly go into the _DATA_ and clear text ones the _CONFIG_ route.</td></tr> <tr><td> </td><td class='diff-context'></td><td> </td><td class='diff-context'></td></tr> <tr><td> </td><td class='diff-context'>== CMMs ==</td><td> </td><td class='diff-context'>== CMMs ==</td></tr> <tr><td>-</td><td class='diff-deletedline'>CMM's register data can be stored in:</td><td>+</td><td class='diff-addedline'>CMM's register can be stored in:</td></tr> <tr><td> </td><td class='diff-context'></td><td> </td><td class='diff-context'></td></tr> <tr><td> </td><td class='diff-context'>'''''cmms'''''/</td><td> </td><td class='diff-context'>'''''cmms'''''/</td></tr> <tr><td colspan="2"> </td><td>+</td><td class='diff-addedline'></td></tr> <tr><td colspan="2"> </td><td>+</td><td class='diff-addedline'>Binary blobs should be preferedly go into the _DATA_ and clear text ones the _CONFIG_ route.</td></tr> <tr><td colspan="2"> </td><td>+</td><td class='diff-addedline'></td></tr> <tr><td colspan="2"> </td><td>+</td><td class='diff-addedline'>== Installation ==</td></tr> <tr><td colspan="2"> </td><td>+</td><td class='diff-addedline'>It is recommended to ask for the XDG variables befor installing globaly visible data on a system. </td></tr> <tr><td colspan="2"> </td><td>+</td><td class='diff-addedline'></td></tr> <tr><td colspan="2"> </td><td>+</td><td class='diff-addedline'>In contrary to create packages with static file locations, like RPM, use the provided static paths only.</td></tr> <tr><td colspan="2"> </td><td>+</td><td class='diff-addedline'></td></tr> <tr><td colspan="2"> </td><td>+</td><td class='diff-addedline'>For ICC profiles this would be:</td></tr> <tr><td colspan="2"> </td><td>+</td><td class='diff-addedline'>: ''/usr/local/share/color/icc''</td></tr> <tr><td colspan="2"> </td><td>+</td><td class='diff-addedline'>: ''/usr/share/color/icc''</td></tr> <tr><td colspan="2"> </td><td>+</td><td class='diff-addedline'>: ''~/.local/share/icc''</td></tr> <tr><td> </td><td class='diff-context'></td><td> </td><td class='diff-context'></td></tr> <tr><td> </td><td class='diff-context'></td><td> </td><td class='diff-context'></td></tr> <tr><td> </td><td class='diff-context'>== Technical implementation ==</td><td> </td><td class='diff-context'>== Technical implementation ==</td></tr> <tr><td>-</td><td class='diff-deletedline'>The profile paths exist on system level in the file hierarchy. </td><td>+</td><td class='diff-addedline'>The profile paths exist on system level in the file hierarchy.</td></tr> <tr><td> </td><td class='diff-context'></td><td> </td><td class='diff-context'></td></tr> <tr><td> </td><td class='diff-context'>For the XDG variables see [1].</td><td> </td><td class='diff-context'>For the XDG variables see [1].</td></tr> </table>

KaiUweBehrmann foobar CMM API 2007-12-19T05:33:12Z 2007-12-19T05:33:12 2007-12-19T05:33:12Z

/* DRAFT */ typo New page<div>= DRAFT = As an excerpt from the current development, I place here a header fragment showing the basic structures to pluging in lcms into Oyranos' module system. My question to interessted developers is, Will the below outlined API be enough to work flawless? /** @brief Oyranos name structure * * @since Oyranos: version 0.1.8 * @date october 2007 (API 0.1.8) */ typedef struct { oyOBJECT_TYPE_e type; /*!< internal struct type oyOBJECT_TYPE_NAME_S */ char * nick; /*!< few letters for mass representation (A1) */ char * name; /*!< normal visible name (A1-MySys) */ char * description; /*!< full user description (A1-MySys from Oyranos) */ } oyName_s; /** @brief icon data * * Since: 0.1.8 */ typedef struct { oyOBJECT_TYPE_e type; /*!< struct type oyOBJECT_TYPE_ICON_S */ int width; int height; float * data; /*!< should be sRGB matched */ oyChar * file_list; /*!< colon ':' delimited list of icon file names, SVG, PNG */ } oyIcon_s; typedef struct oyCMMapi_s oyCMMapi_s; === CMM Registration === /** @brief the CMM API resources struct to implement and set by a CMM * * Given an example CMM with name "little cms", and it 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". * * Oyranos will scan the $(libdir)/color/cmms/ path, opens the available * CMM's from this directory and extracts the four-chars before OY_MODULE_NAME * from the library names. Module paths can be added through the * OY_MODULE_PATHS environment variable. * Oyranos looks for a symbol to a oyCMMInfo_s struct of the four-byte ID plus * OY_MODULE_NAME which results in our example in the name "lcms_cmm_module". * On Posix system this should be loadable by dlsym. * The lcms_cmm_module should be of type oyCMMInfo_s with the type field * and all other fields set appropriately. * * The api field is a placeholder to get a real api struct assigned. If the CMM * wants to provide more than one API, they can be chained. The apis_n member * is to be set to the number of APIs. * * @since Oyranos: version 0.1.8 * @date 5 december 2007 (API 0.1.8) */ typedef struct { oyOBJECT_TYPE_e type; /*!< struct type oyOBJECT_TYPE_CMM_INFO_S */ icSignature cmmId; /*!< ICC signature 'lcms' */ oyChar * backend_version; /*!< non localisable 'v1.17' */ oyName_s name; /*!< localisable 'lcms' 'little cms' '...'*/ oyName_s manufacturer; /*!< localisable 'Marti' 'Marti Maria' 'support email: @; internet: www.littlecms.com; sources: ...' */ oyName_s copyright; /*!< localisable 'MIT','MIT License'.. */ int oy_compatibility; /*!< last supported Oyranos CMM API : OYRANOS_VERSION */ oyCMMapi_s * api; /**< must be casted to a according API */ int apis_n; /**< count of implemented apis */ oyIcon_s icon; /*!< zero terminated list of a icon pyramid */ } oyCMMInfo_s; typedef void* oyPointer; typedef oyPointer (*oyStructCopyF_t) ( oyPointer, oyPointer ); typedef int (*oyStructReleaseF_t) ( oyPointer* ); /** @brief CMM pointer * * The oyCMMptr_s is used internally and for CMM's. * Memory management is done by Oyranos' oyAllocateFunc_ and oyDeallocateFunc_. * * @since Oyranos: version 0.1.8 * @date november 2007 (API 0.1.8) */ typedef struct { oyOBJECT_TYPE_e type; /*!< internal struct type oyOBJECT_TYPE_CMM_POINTER_S */ char cmm[5]; /*!< the 4 char CMM ID 'lcms' */ char func_name[32]; /*!< optional the CMM's function name */ oyPointer ptr; /*!< a CMM's data pointer */ char resource[5]; /**< the resource type 'oyPR' */ oyStructReleaseF_t ptrRelease; /*!< CMM's deallocation function */ int ref; /**< Oyranos reference counter */ } oyCMMptr_s; === Pixel Layout === typedef enum { oyUINT8, /*!< 8-bit integer */ oyUINT16, /*!< 16-bit integer */ oyUINT32, /*!< 32-bit integer */ oyHALF, /*!< 16-bit floating point number */ oyFLOAT, /*!< IEEE floating point number */ oyDOUBLE /*!< IEEE double precission floating point number */ } oyDATATYPE_e; /** parametric enum as shorthand for the channel layout in bitmaps should fit into a 32bit type, usual unsigned int or uint32_t X F P S TTTT OOOOOOOO CCCCCCCC C channels count per pixel (3 for RGB); max 255 O colour channel offset (0 for RGB, 1 for ARGB) P Planar bool: 0 - interwoven, 1 - one channel after the other S Swap colour channels bool (BGR) T Type oyDATATYPE_e X non host byte order F Revert bool: 0 - MinIsBlack(Chocolate) 1 - MinIsWhite(Vanilla); exchange min and max : (1-x) */ The above pixel description is slightly different from lcms layout as it relies on the addtional profile information, to avoid concurrent definitions for the colour channels. /** @brief CMM capability query enum * * Since: 0.1.8 */ typedef enum { oyQUERY_OYRANOS_COMPATIBILITY, /*!< provides the Oyranos version and expects the CMM compiled or compatibility Oyranos version back */ oyQUERY_PIXELLAYOUT_DATATYPE, /*!< takes a oyDATATYPE_e arg as value */ oyQUERY_PIXELLAYOUT_CHANNELCOUNT, oyQUERY_PIXELLAYOUT_SWAP_COLOURCHANNELS, oyQUERY_PIXELLAYOUT_COLOURCHANNEL_OFFSET, oyQUERY_PIXELLAYOUT_PLANAR, oyQUERY_PIXELLAYOUT_FLAVOUR, oyQUERY_HDR, /*!< value a oyDATATYPE_e (oyHALF...) */ oyQUERY_PROFILE_FORMAT = 20 /*!< value 1 == ICC */ } oyCMMQUERY_e; typedef int (*oyCMMCanHandle_t) ( oyCMMQUERY_e type, int value ); typedef int (*oyCMMInit_t) ( void ); typedef int (*oyCMMProfile_Open_t)( oyPointer block, size_t size, oyCMMptr_s * oy ); #define oyCMM_PROFILE "oyPR" typedef int (*oyCMMColourConversion_Create_t) ( oyCMMptr_s ** cmm_profile_array, int profiles_n, int pixel_layout_in, int pixel_layout_out, int intent, int proofing_intent, int flags, oyCMMptr_s * oy ); #define oyCMM_COLOUR_CONVERSION "oyCC" typedef void (*oyCMMProgress_t) ( int ID, double progress ); typedef int (*oyCMMColourConversion_Run_t)( oyCMMptr_s * cmm_transform, oyPointer in_data, oyPointer out_data, int count, oyCMMProgress_t progress ); typedef icSignature (*oyCMMProfile_GetSignature_t) ( oyCMMptr_s * cmm_ptr, int pcs); /*oyPointer oyCMMallocateFunc ( size_t size ); void oyCMMdeallocateFunc(oyPointer mem );*/ typedef int (*oyCMMMessageFuncSet_t)( oyMessageFunc_t message_func ); /** @brief the generic part if a API to implement and set by a CMM * * @since Oyranos: version 0.1.8 * @date 12 december 2007 (API 0.1.8) */ struct oyCMMapi_s { oyOBJECT_TYPE_e type; /**< struct type oyOBJECT_TYPE_CMM_API1_S */ oyCMMapi_s * next; oyCMMInit_t oyCMMInit; oyCMMMessageFuncSet_t oyCMMMessageFuncSet; }; /** @brief the API 1 to implement and set by a CMM * * @since Oyranos: version 0.1.8 * @date 5 december 2007 (API 0.1.8) */ typedef struct { oyOBJECT_TYPE_e type; /**< struct type oyOBJECT_TYPE_CMM_API1_S */ oyCMMapi_s * next; oyCMMInit_t oyCMMInit; oyCMMMessageFuncSet_t oyCMMMessageFuncSet; oyCMMCanHandle_t oyCMMCanHandle; oyCMMProfile_Open_t oyCMMProfile_Open; oyCMMProfile_GetText_t oyCMMProfile_GetText; oyCMMProfile_GetSignature_t oyCMMProfile_GetSignature; oyCMMColourConversion_Create_t oyCMMColourConversion_Create; oyCMMColourConversion_Run_t oyCMMColourConversion_Run; } oyCMMapi1_s; === Discussion === The oyCMMColourConversion_Create_t function seems the most complex one. It covers the profile set, proofing, rendering intent, precission, gamut checking and so on. The provided oyCMMptr_s "oy" struct has to be filled in with the appropriate values, a pointer and release function and can contain additional hints to allow some runtime typechecking in both the CMM itself and Oyranos. typedef int (*oyCMMColourConversion_Create_t) ( oyCMMptr_s ** cmm_profile_array, int profiles_n, int pixel_layout_in, int pixel_layout_out, int intent, int proofing_intent, int flags, oyCMMptr_s * oy ); #define oyCMM_COLOUR_CONVERSION "oyCC" The pixel_layout_xx is described in the "parametric enum" comment. The profiles need to follow a certain order to make sense for proofing. Or it would be more secure to have the proofing profile as a extra parameter? The intent and proofing intent should be clear. The flags are open to discuss. They need to cover gamut checking and the BPC algorithm. Optionally it could cover the no precalculation flag known from lcms to increase precision, selection of the interpolation (tetrahedral versus trilinear) and other speed flags. K channel preservation stuff? cmsFLAGS_GRIDPOINTS ? What is missed or is unclear, at least to me, are the CIE CAM02 handling, on disk transform caching and profile creation in the API. Probably it is enough to handle the last points later. The oyCMMCanHandle_t function will be merged as a static field into the oyCMMapi1_s struct.</div>

KaiUweBehrmann foobar Oyranos 2007-12-18T12:57:41Z 2007-12-18T12:57:41 2007-12-18T12:57:41Z

/* Development */ <table border='0' width='98%' cellpadding='0' cellspacing='4' class='diff'> <tr> <td colspan='2' width='50%' align='center' class='diff-otitle'>Revision as of 12:57, 18 Dec 2007</td> <td colspan='2' width='50%' align='center' class='diff-ntitle'>Current revision</td> </tr> <tr><td colspan="2" align="left">Line 49:</td> <td colspan="2" align="left">Line 49:</td></tr> <tr><td> </td><td class='diff-context'>* [[FeatureWish|Feature wishes]] including a Todo list for the next release</td><td> </td><td class='diff-context'>* [[FeatureWish|Feature wishes]] including a Todo list for the next release</td></tr> <tr><td> </td><td class='diff-context'>* [[FeatureWish#Todo|Todo]] list for usual bigger milestones and the next release</td><td> </td><td class='diff-context'>* [[FeatureWish#Todo|Todo]] list for usual bigger milestones and the next release</td></tr> <tr><td colspan="2"> </td><td>+</td><td class='diff-addedline'>* [[CMM API]]</td></tr> <tr><td> </td><td class='diff-context'>* [[Concepts]] to gather ideas for Oyranos</td><td> </td><td class='diff-context'>* [[Concepts]] to gather ideas for Oyranos</td></tr> <tr><td> </td><td class='diff-context'>* historical draft [http://www.behrmann.name/cms/cms_skeleton_v1.html CMS skeleton] at behrmann site</td><td> </td><td class='diff-context'>* historical draft [http://www.behrmann.name/cms/cms_skeleton_v1.html CMS skeleton] at behrmann site</td></tr> </table>

KaiUweBehrmann foobar FeatureWish 2007-12-18T12:53:59Z 2007-12-18T12:53:59 2007-12-18T12:53:59Z

/* ICC profile handling */ <table border='0' width='98%' cellpadding='0' cellspacing='4' class='diff'> <tr> <td colspan='2' width='50%' align='center' class='diff-otitle'>Revision as of 12:53, 18 Dec 2007</td> <td colspan='2' width='50%' align='center' class='diff-ntitle'>Current revision</td> </tr> <tr><td colspan="2" align="left">Line 26:</td> <td colspan="2" align="left">Line 26:</td></tr> <tr><td> </td><td class='diff-context'>{| style="width:100%;text-align:left" colspan="20"</td><td> </td><td class='diff-context'>{| style="width:100%;text-align:left" colspan="20"</td></tr> <tr><td> </td><td class='diff-context'>|-</td><td> </td><td class='diff-context'>|-</td></tr> <tr><td>-</td><td class='diff-deletedline'>| Progress 10%</td><td>+</td><td class='diff-addedline'>| Progress 15%</td></tr> <tr><td> </td><td class='diff-context'>| Version: x.x.x</td><td> </td><td class='diff-context'>| Version: x.x.x</td></tr> <tr><td> </td><td class='diff-context'>| Start: 2006</td><td> </td><td class='diff-context'>| Start: 2006</td></tr> <tr><td colspan="2" align="left">Line 73:</td> <td colspan="2" align="left">Line 73:</td></tr> <tr><td> </td><td class='diff-context'></td><td> </td><td class='diff-context'></td></tr> <tr><td> </td><td class='diff-context'>==== Directory Paths ====</td><td> </td><td class='diff-context'>==== Directory Paths ====</td></tr> <tr><td>-</td><td class='diff-deletedline'>* [[OpenIccDirectoryProposal|ICC profile path specification]]</td><td>+</td><td class='diff-addedline'>* [[OpenIccDirectoryProposal|OpenICC path specification]]</td></tr> <tr><td> </td><td class='diff-context'>{| style="width:100%;text-align:left" colspan="20"</td><td> </td><td class='diff-context'>{| style="width:100%;text-align:left" colspan="20"</td></tr> <tr><td> </td><td class='diff-context'>|-</td><td> </td><td class='diff-context'>|-</td></tr> <tr><td colspan="2" align="left">Line 82:</td> <td colspan="2" align="left">Line 82:</td></tr> <tr><td> </td><td class='diff-context'>|-</td><td> </td><td class='diff-context'>|-</td></tr> <tr><td> </td><td class='diff-context'>|}</td><td> </td><td class='diff-context'>|}</td></tr> <tr><td>-</td><td class='diff-deletedline'>* ICC_PROFILE_PATH ? how to interact with Oyranos</td><td>+</td><td class='diff-addedline'>* (obsoleted by XDG variables) ICC_PROFILE_PATH ? how to interact with Oyranos</td></tr> <tr><td> </td><td class='diff-context'>* update Oyranos' internal path representation to the [[OpenIccDirectoryProposal|OpenICC Directory Proposal]]</td><td> </td><td class='diff-context'>* update Oyranos' internal path representation to the [[OpenIccDirectoryProposal|OpenICC Directory Proposal]]</td></tr> <tr><td colspan="2"> </td><td>+</td><td class='diff-addedline'>* (done) OY_MODULE_PATHS for CMM's</td></tr> <tr><td> </td><td class='diff-context'></td><td> </td><td class='diff-context'></td></tr> <tr><td> </td><td class='diff-context'>=== Standard Profiles ===</td><td> </td><td class='diff-context'>=== Standard Profiles ===</td></tr> <tr><td colspan="2" align="left">Line 102:</td> <td colspan="2" align="left">Line 103:</td></tr> <tr><td> </td><td class='diff-context'>|-</td><td> </td><td class='diff-context'>|-</td></tr> <tr><td> </td><td class='diff-context'>| style="width:1%" |</td><td> </td><td class='diff-context'>| style="width:1%" |</td></tr> <tr><td>-</td><td class='diff-deletedline'>| style="width:20%" | Progress: 0%</td><td>+</td><td class='diff-addedline'>| style="width:20%" | Progress: 60%</td></tr> <tr><td> </td><td class='diff-context'>| style="width:20%" | Version: x.x.x</td><td> </td><td class='diff-context'>| style="width:20%" | Version: x.x.x</td></tr> <tr><td> </td><td class='diff-context'>| style="width:20%" | Start: 2007</td><td> </td><td class='diff-context'>| style="width:20%" | Start: 2007</td></tr> <tr><td>-</td><td class='diff-deletedline'>| style="width:20%" | Assigned to: Scribus?</td><td>+</td><td class='diff-addedline'>| style="width:20%" | Assigned to: Kai-Uwe Behrmann (Scribus?)</td></tr> <tr><td> </td><td class='diff-context'>|-</td><td> </td><td class='diff-context'>|-</td></tr> <tr><td> </td><td class='diff-context'>|}</td><td> </td><td class='diff-context'>|}</td></tr> <tr><td>-</td><td class='diff-deletedline'>** transform caching (file format)</td><td>+</td><td class='diff-addedline'>** transform caching (file format?)</td></tr> <tr><td> </td><td class='diff-context'>* frontend API, transforms, caching, image description - buffer layout / screen position</td><td> </td><td class='diff-context'>* frontend API, transforms, caching, image description - buffer layout / screen position</td></tr> <tr><td> </td><td class='diff-context'>{| style="width:100%;text-align:left" colspan="20"</td><td> </td><td class='diff-context'>{| style="width:100%;text-align:left" colspan="20"</td></tr> <tr><td> </td><td class='diff-context'>|-</td><td> </td><td class='diff-context'>|-</td></tr> <tr><td> </td><td class='diff-context'>| style="width:1%" |</td><td> </td><td class='diff-context'>| style="width:1%" |</td></tr> <tr><td>-</td><td class='diff-deletedline'>| style="width:20%" | Progress: 5%</td><td>+</td><td class='diff-addedline'>| style="width:20%" | Progress: 55%</td></tr> <tr><td> </td><td class='diff-context'>| style="width:20%" | Version: 1.x.x</td><td> </td><td class='diff-context'>| style="width:20%" | Version: 1.x.x</td></tr> <tr><td> </td><td class='diff-context'>| style="width:20%" | Start: 2007</td><td> </td><td class='diff-context'>| style="width:20%" | Start: 2007</td></tr> </table>

KaiUweBehrmann foobar Standards 2007-12-14T07:52:36Z 2007-12-14T07:52:36 2007-12-14T07:52:36Z

/* File Formats */ <table border='0' width='98%' cellpadding='0' cellspacing='4' class='diff'> <tr> <td colspan='2' width='50%' align='center' class='diff-otitle'>Revision as of 07:52, 14 Dec 2007</td> <td colspan='2' width='50%' align='center' class='diff-ntitle'>Current revision</td> </tr> <tr><td colspan="2" align="left">Line 69:</td> <td colspan="2" align="left">Line 69:</td></tr> <tr><td> </td><td class='diff-context'>* [http://www.remotesensing.org/libtiff/document.html '''T'''agged '''I'''mage '''F'''ile '''F'''ormat] at remotesensing.org</td><td> </td><td class='diff-context'>* [http://www.remotesensing.org/libtiff/document.html '''T'''agged '''I'''mage '''F'''ile '''F'''ormat] at remotesensing.org</td></tr> <tr><td> </td><td class='diff-context'>* [http://www.jpeg.org/jpeg/ '''J'''oint '''P'''hotographic '''E'''xperts '''G'''roup]</td><td> </td><td class='diff-context'>* [http://www.jpeg.org/jpeg/ '''J'''oint '''P'''hotographic '''E'''xperts '''G'''roup]</td></tr> <tr><td>-</td><td class='diff-deletedline'>* [http://www.libpng.org/pub/png/spec/iso/ '''P'''ortable '''N'''etworks '''G'''raphic]</td><td>+</td><td class='diff-addedline'>* [http://www.libpng.org/pub/png/spec/iso/ '''P'''ortable '''N'''etworks '''G'''raphic] + [http://www.w3.org/TR/2003/REC-PNG-20031110/#4Concepts.ColourSpaces W3C] documentation</td></tr> <tr><td> </td><td class='diff-context'>* [http://www.adobe.com/devnet/pdf/pdf_reference.html '''P'''ortable '''D'''ocument '''F'''ormat] at Adobe</td><td> </td><td class='diff-context'>* [http://www.adobe.com/devnet/pdf/pdf_reference.html '''P'''ortable '''D'''ocument '''F'''ormat] at Adobe</td></tr> <tr><td> </td><td class='diff-context'>* [http://www.w3.org/TR/SVG/color.html '''S'''calable '''V'''ector '''G'''raphics] at w3</td><td> </td><td class='diff-context'>* [http://www.w3.org/TR/SVG/color.html '''S'''calable '''V'''ector '''G'''raphics] at w3</td></tr> </table>

KaiUweBehrmann foobar