Hello,
sorry for the full quote. But it provides us a record.
Am 01.08.2014 09:46, schrieb Joseph Simon:
> Hi Kai-Uwe,
>
> On Thu, Jul 31, 2014 at 3:50 AM, Kai-Uwe Behrmann <k...@gmx.de> wrote:
>
>> The mockup looks good to me. As the new cm flag should apply to all
>> device classes, it could reside in oyranos_devices.c .
I think now ,that is not needed. You can add the below call in
kmdevices.cpp and that's it.
>> oyConfig_GetOptions("backend_core") is maybe the easiest way to add the
>> flag to a device.
>>
> I thought so. Any changes made through KolorManager must be carried across
> to other programs. So, it is a matter of writing the code to store the flag
> status (likely, within kmdevices) and loading it (an Oyranos interface
> elsewhere).
agreed. That should be documented in the device protocoll?
http://www.oyranos.org/wiki/index.php?title=Device_Settings#Module_Protocol
https://github.com/oyranos-cms/oyranos/blob/master/doc/doxymentation_alpha#L224
> Regarding the UI, every "check" in the cm-enable/disable switch should also
> hide all of the ICC profile selection boxes below and remove a profile from
> that device.
Removing the profile is no guarantee, as Oyranos still searches for a
best matching profile for a given device, like those generated with
dispcalGUI and installed from Taxi DB. Otherwise I agree and would like
to implement that in some applications.
> Can I further reply to the email list?
> Sure.
kind regards
Kai-Uwe
>> Note, the actual repositories switched to:
>> https://github.com/oyranos-cms
>>
> Yup. That is where I cloned it from.
>
>
>> kind regards
>> Kai-Uwe
>>
> Joe
>
>
>
>
>> Am 30.07.2014 23:40, schrieb Joseph Simon:
>>> Hi Kai-Uwe,
>>>
>>> I have attached a sample UI, with the added CM switch in Kolor Manager.
>>>
>>> There needs to be something registered in the DB/backend to mark each
>>> device as being "color managed enabled" (by default) or "CM disabled".
>>> Where in Oyranos Git can be best used to add such code?
>>>
>>> Joe
>>>
>>>
>>> On Mon, Jul 28, 2014 at 1:36 AM, Kai-Uwe Behrmann <k...@gmx.de> wrote:
>>>
>>>> Hello Joe,
>>>>
>>>> glad to read from you.
>>>>
>>>> Yes, you can certainly add a device CM disable flag. That feature is
>>>> fine with me too.
>>>>
>>>> kind regards
>>>> Kai-Uwe
>>>>
>>>> Am 26.07.2014 10:02, schrieb Joseph Simon:
>>>>> Dear Kai-Uwe,
>>>>>
>>>>> It has been a long time. I have not been programming in a while due to
>> a
>>>>> sort of change in life plans; Please do not take the incommunicado
>>>>> personally.
>>>>>
>>>>> Currently, there is a 'device_inhibit' flag in cups-filters that
>> disables
>>>>> color management printing if it is "true/1". It seems that Colord is
>> able
>>>>> to raise this flag if its color manager specifies that the device -
>>>> printer
>>>>> in this case - is registered as "color management disabled".
>>>>>
>>>>> I have asked Till if it is okay if we can make this case available to
>> ALL
>>>>> color managers, and he agreed to it (although he does not wish to make
>>>>> cups-filters dependent on every color manager).
>>>>>
>>>>> Are you okay with me modifying KolorManager so that printers can be set
>>>>> color-managed/non-color-managed in the UI, and then have those settings
>>>>> registered in cups-filters? A file similar to colord.c would need to be
>>>>> added (oyranos.c?) in cups-filters.
>>>>>
>>>>> Joe Simon
>>>>>
>>
------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Oyranos-devel mailing list
Oyranos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oyranos-devel
