[OpenICC] transform cache

[Kai-Uwe Behrmann]

further thoughts beyond transformations:

A:
osX uses color worls , which seems to be similiar to an context driven 
environment. All setting are putted in an structure and allway refered to 
while using cms functions. Well this would extend my more technical 
transform approach.

B:
An other concept is the state model. Settings remains saved and 
usually functions are affected by these settings without further 
reference (OpenGL).

C:
Last but not least, every action needs the full set of arguments to make 
it valid and beheaving as intended.

In CinePaint uses currently the model C with a slightly A coupled 
approach.

What does other projects do? What concept would fit best? Other ideas?

regards
Kai-Uwe Behrmann
                                + development for color management 
                                + imaging / panoramas
                                + email: ku.b at gmx.de
                                + http://www.behrmann.name


Am 14.12.04, 11:02 +0100 schrieb Kai-Uwe Behrmann:

> Hi,
> 
> as I understood transforms (as used by lcms and maybe others as well) are
> the same like device link profiles. Can then an transform caching beeing
> done by using devicelink profiles for all CMMs? This would simply the
> transform handling mechanism. Oyranos could provide the storage logic.
> 
> char* oyGetTransform(char** profileNames, int nProfiles, int flags);
> 
> The retrieved char* would contain an valid device link profile name in the
> first stage or zero.
> In an later stage, the returned string can contain an transform identifier
> used to let oyranos pass the transforming function call to the plugged and
> current CMM.
> 
> --
> Kai-Uwe Behrmann
>                                 + imaging development / panoramas
>                                 + color management
>                                 + email: ku.b at gmx.de
>                                 + CMS proposal <www.behrmann.name>
>