[Openicc] Gsoc2010 - oyranos API stabilization project

[Yiannis Belias]

Hi,

OK, so here is a list of the Modules and the proposed actions to be taken:
o Miscellaneous->Generic Objects
o Miscellaneous->Values Handling
o Module APIs
o Device API
o Profile API
o Named Colour API

(a) Simplify the interconnections of objects.
(b) Change the implementation code of objects to use an internal and public
   API by using the code generator. Copy the rest of the already existing code to new object.
(c) Create test cases.
(d) Write documentation.

(a) seems a little fuzzy right now, it probably needs some conceptual work first
to reorganize the object dependencies.
So, I hope I'm getting this right. Any additions/modifications to this plan?

Cheers,
Yiannis

> Currently Oyranos is rather complex. The configuration parts are
> exposed by a limited stable API and the object oriented stuff as used in
> kolor-manager and ICC Examin. The CMM related graph handling is interwoven
> with configuration constraints and the UI exposition through XFORMS[1]. So
> often enough APIs can not be exposed separately, say the CMM part for
> colour conversion or the named colour API, which have otherwise not
> changed much in recent months.
> 
> 
> Oyranos has a small C code generator[2] for object oriented structures and
> belonging functions. I started to support spliting object code into
> public generic structures and a internal full blown object part. This
> could be used to generate most objects structures from scratch and port
> the actual functionality by copy and past. Adding missed tests for the
> ported APIs would be of good help through the process.
> This would be a large part of the project and allow the profile, device
> configuration and possibly named colour APIs to become supportable in a
> stable API.
> 
> 
> kind regards
> Kai-Uwe Behrmann