Oyranos/FeatureWish
From ColourWiki
(Redirected from FeatureWish)
| Table of contents |
[edit]
Feature Wishes for Oyranos
They come often from discussions at the OpenICC email list. It is a good place to annotate, suggest, or ask. Writing here is better than forget elsewhere. The assigment of items to a person does not mean there happens currently work. So offering help is better than waiting with a item of interesst.
A closely related source for project ideas is the Google Summer of Code wiki page of OpenICC (http://www.freedesktop.org/wiki/OpenIcc/GoogleSoC2009).
[edit]
Devices
- (done as pddt) implement Device_Settings in ICC profiles
| Progress: 100% [done] | Target: 0.1.10 | Start: 2008.00.00 | Assigned to: Kai-Uwe Behrmann |
- generalise to Sane, CUPS ... see as well here
| Progress: 98% [done] | Target: 0.1.10 | Start: 2009.03.00 | Assigned to: Kai-Uwe Behrmann, Yiannis Belias |
- publicise the device module communication protocol on a separate ColourWiki page
- integrate into the KDE Kolormanager (http://code.google.com/soc/2008/openicc/appinfo.html?csaid=9EFC0E521D25020) mentored by OpenICC developers
| Progress: 75% [done] | Target: 0.1.10 | Start: 2008.03.00 | Assigned to: Joe Simon, Hal V. Engel, Cyrille Berger, Kai-Uwe Behrmann |
[edit]
Monitor
- check for validity of a display setup (calibrated: yes/no, expired, ...)
- done (add non EDID monitor support - by a mix of X description and by Xinerama geometry (prepared for 0.1.8))
| Progress: 100% [done] | Target: 0.1.8 | Start: 2007.08.00 | Assigned to: Kai-Uwe Behrmann |
- done (common screen naming sheme for X11, osX and Windows)
- Named Colours in X11, osX ,Windows representation
- clear about VCGT handling, use Xcalib (licensing?) or ArgyllCMS, give at least a hint at configure time "found Xcalib/Argyll - can load VCGT"
- support the upcomming X11 CM protokolls (http://www.freedesktop.org/wiki/OpenIcc/ColorManagementNearX) developed by Tomas Carnecky. implemented in graph buit need darfting/specification
- done (XRandR support)
[edit]
ICC profile handling
- check for well behaving of Editing colour spaces (Matrix, RGB: gamma equally over all channels, Gray axis, ...)
- check ICC profiles
| Progress 25% | Version: x.x.x | Start: 2006 | Assigned to: Kai-Uwe Behrmann |
- extraction of colorimetric informations from a profile like primaries, gamma or profile type
[edit]
Settings and Policies
- use of standard folders for: display profiles, RGB editing profiles, CMYK editing profiles.
If advanced users want to use special profiles e.g. for editing, they have manually to add the profile to this folder. This is an easy way to implement a solution, that beginners are not able to choose wrong profiles by accident.
- color management policies
| Progress 70% | Version: 0.1.x | Start: 2004 | Assigned to: Kai-Uwe Behrmann |
- done (only allow flat color documents or allow mixed mode documents ?)
- done (how to deal with profile mismatches during opening files ?)
- done (how to deal with profile mismatches during placing content ?)
- to add:
- done (add CMYK editing profile (OY_DEFAULT_EDITING_CMYK_PROFILE))
- done (add non-editable web colour space sRGB for displaying - should be used during download from web (OY_DEFAULT_WEB_PROFILE=sRGB))
- done (profile assigning for untagged data during opening (auto / leave / ask) (OY_UNTAGGED_ASSIGN_ACTION))
- done (add RGB/CMYK opening mismatch policy (convert / leave attached profile/pop-up) , in an pure sRGB environment it could be used to make all unknown RGB content equal (OY_MISMATCH_RGB_OPEN_ACTION ...))
- done (profile assigning for mismatched data during editing policy, harmonise during editing for homogeneous colour space documents (OY_MISMATCH_CMYK_CHANGE_ACTION ...))
- note: placing and editing files could equal react regarding mismatch (handles the mismatch question from above)
- mixed colour space documents for internet warning/quiet (OY_MIXED_COLOUR_INTERNET_DOCUMENT_WARNING)
- rendering intent (Craig Ringer's suggestion) (http://lists.freedesktop.org/archives/openicc/2007q4/000963.html)
- Perceptual
- Relative Colorimetric with BPC
- -- Rarely Needed --
- Relative Colorimetric without BPC
- Absolute Colorimetric
- Saturation
- Reference: AdobeBPC spec (http://www.adobe.com/devnet/photoshop/sdk/AdobeBPC.pdf)
- allow non persistent settings, examples:
- useful for temporarily adding profile paths in osX bundles
- switching default profiles to gamma 1.0 versions in one application, without touching other applications
[edit]
Directory Paths
| Progress: 100% | Version: x.x.x | Start: defacto 2004 | Assigned to: open |
- (obsoleted by XDG variables) ICC_PROFILE_PATH ? how to interact with Oyranos
- (done) update Oyranos' internal path representation to the OpenICC Directory Proposal
- (done) OY_MODULE_PATHS for CMM's
[edit]
Default Profiles
- naming of ECI profiles to something FOGRA corresponding (Chris Murphy and others on OpenICC)
- most ECI profiles are replaced with Argyll created ones
- remains to relicense or replace the eciRGB ones
- country specific settings
| Progress: 90% | Version: 0.1.8 | Start: | Assigned to: Kai-Uwe Behrmann |
[edit]
CMM Framework
- backend API a typical CMM should provide
- (done) transform caching (file format - device link)
| Progress: 75% | Version: x.x.x | Start: 2007 | Assigned to: Kai-Uwe Behrmann (Scribus?) |
- frontend API, transforms, caching, image description - buffer layout / screen position
| Progress: 70% | Version: 1.x.x | Start: 2007 | Assigned to: Kai-Uwe Behrmann |
- Oyranos/Null Transform Checking - implicite; beside explicite opt out support in options
| Progress: 0% | Version: 1.x.x | Start: 2008 | Assigned to: ? |
- options handling (xml, GUI)
- static options should be displayed to users according to preferences (for instance mismatch option)
- options handling (xml, GUI)
| Progress: 25% | Version: x.x.x | Start: 2006 | Assigned to: Kai-Uwe Behrmann + ? |
| Progress: 20% | Version: 1.x.x | Start: 2008 | Assigned to: Marijana Novakovic |
- file support (tiff,png,jpeg), move from Colori
| Progress: 25% | Version: first use in Colori | Start: 2007-09-10 | Assigned to: Kai-Uwe Behrmann |
[edit]
Named Colour
- colour information structure
| Progress: 30% | Version: first use in ICC Examin v0.45 | Start: 2007-09-03 | Assigned to: Kai-Uwe Behrmann |
Constitute a colour patch presentation:
- done - CIELab representation
- done - arbitrary channels (32)
- done - channel characterisation (4 byte ICC signature)
- done - channel names list
- done - colour name
- done - colour description
- done - colour nick name
- done - colour reference (ICC profile)
- done - cgats representation, this can contain additional observer characteristics or spectral data
- current state is shown here (http://www.behrmann.name/wind/oyranos/icc_examin_2007.09.24.html)
- done - allow for grouping ( swatches )
- exchange as colour selection(s) in X11, Quartz ...
- Named Colours (oyNamedColour(s)_s) <-> data blob (Create's colour swatch XML, CGATS, ...) in a plugable fashion
- keep in sync with Create (http://create.freedesktop.org/wiki/index.php?title=Swatches_-_colour_file_format)
- HDR range information
- creator signature?
- gamut warning with the device, which is exceeded - monitor, printer, colour space
- to sRGB float conversion from Lab(D50)/XYZ or from channels over ICC profile with lcms
- gamma handling?
- extra channel handling (sheme fo explicitely naming alpha, UV ...) enums? string tags? ...
[edit]
Miscellaneous
- done (split Oyranos headers for users, configuration)
- done (show in headers only stable functions)
- done (remove unstable functions from descriptions)
- later show only advanced options to those users who like it
- something like default settings / policy
- and modify policy, advanced or custom
- done(v0.1.5) Bob Friesenhahn suggested Oyranos should be completely relocatable
- publicate Colori
- IPC
[edit]
Todo
Oyranos Roadmap
[edit]
Target 1.0.0
- see inline (http://www.oyranos.org/doc/html/concept_1.0.html) documentation
[edit]
Target 0.1.10
[edit]
Target 0.1.8
- (done) error handling
- (done) information callback function:
int (*callback)(int code, const char* format, ...)
- internally all can stay with macros
- the context should remain distinguishable, as over a pointer or a ID, the anonymous callback design above is problematic for OO programming
- override default settings, dependent whether they are inbuild or explicitely set by a user [1] (http://www.behrmann.name/wind/cinepaint/cinepaint_2007.04.13_1.html): delayed until options are inside a oyOptions_s objetc
- (done) gray profile setting
- (done) license change as stated (http://www.oyranos.org/#license)
- (done) new default profiles from ECI (http://www.eci.org/eci/de/060_downloads.php)
- (done) investigate in ColorSync ignoring some CMM:SGI marked profiles
- (done) look into newer Elektra library API (Oyranos v0.1.7 can use Elektra v0.6.4) v0.1.8 uses Elektra v0.7.x(which waits for its release)
[edit]
External
- Fedora bug entry (https://bugzilla.redhat.com/show_bug.cgi?id=239936)
