Closed beku closed 9 years ago
The third point from above appears complicated. Device modules could simply load their rank maps from a canonical place. Say OY_DATADIR/color/rank-map .
device filters load now json rank maps, missed is SANE
SANE is worked on.
SANE devices are visible. Even if this module needs work, this issue is done.
make the oyCMMapi8_s object fully dynamically creatable. This will allow to build a device filter from a rank_map only. Rank maps can be created from JSON by oyRankMapFromJSON() or by oyRankMap * oyGetRankMapFromDB ( const char* registration ). For better integration with the device filter driven configuration, it would be easier to use a normal oyCMMapi8_s filter object and skip any extra rank_map only logic. Main goal is to support abstract the device DB handling out and allow users to skip a full blown oyCMMapi8_s implementation by using light weight JSON communication. ° create dynamic oyCMMapi8_s API's like for oyCMMapi4_s ° create oyCMMapi8_s filters from rank_maps in oyGetRankMapFromDB() ° store existing device filter rankmaps as JSON and add them to these filters during load time; possibly in oyCMMsGetFilterApis()