OpenICC

Web Page: http://www.freedesktop.org/wiki/OpenIcc/GoogleSoC2012

Mailing List: http://lists.freedesktop.org/mailman/listinfo/openicc

OpenICC consists of members from various open source projects, commercial vendors and color management experts who use the OpenICC email list as a meeting place to work out issues related to color management in the open source ecosystem. It was started by some Scribus team members to better support introduction of color management into applications and discuss general issues related to color management. List contributors are application and CMS developers as well as color management specialists and users, no matter whether commercial, open source and both together.  The participants come from an exceptionally broad range of organizations and backgrounds.  This includes many open source projects such as Scribus, GIMP, Inkscape, CUPS,  OpenPrinting, XOrg, GutenPrint, KDE, GNOME, Krita, ArgyllCMS, LProf, LCMS, SANE, UFRAW and others.  There are also many commercial organizations represented as well including Lexmark and Adobe.   OpenICC also sponsors one of our members to participate as representive of OpenICC in the International Color Consortium (ICC).

Projects

• Color-Managed Printing for Krita This project will focus on adding color-managed printing for Krita, KDE's draw & paint application. By using the newly-developed libCmpx (Color-Managed Printing eXtension) interface, this project will extend Krita's print dialog to allow for "smart" ICC profile selection, as well as providing the means to attach profile data into the Linux print chain.
• KWin Colour Correction The goal is to implement coluor correction for the KDE workspace, by using Oyranos for creating colour transforms, and by complying to the X Color Management specification, with the help of libXcm.
• SimpleUI - Simple Toolkit Abstraction Many a times, projects are written which require various plug-ins and user inputs for some configuration parameters. Those plug-ins present their own user interface, not necessarily in same language or platform, resulting in inconsistency for porting the projects on other platforms. Most of the times, it defeats the purpose of writing and making that projects. Hence, we require some system such that UI's do not pose obstacle in building such projects. Eg, suppose you have a project which requires use of some plug-in which only has a qt front-end. Hence, all other users , like that of gnome, windows, mac, etc will be forced to use command line, or worse, settle themselves with default values, simply because UI of some plug-in or module does not work on their platform. It lets the users of the project down, and hence a lack of confidence in that project. Also, projects somewhere resist themselves in using such plugins. Similarly, oyranos colour management system is in parts only a thin layer between imaging applications and advanced modules or plug-ins. To deploy these plug-ins flexible and maintain toolkit independency, plug-ins must present some consistent UI. SimpleUI tries to solve this problem. It creates a set of functions and widgets in standard formats which can be used for user input as such, as well allow programs to display their UI's for a specific UI library like gtk or qt. Goal is to create a simple and highly flexible GUI system, which allows easy creation of dialogs including callback mechanisms, advance UI configuration as well as platform independency.