Thread: [Lcms-user] LittleCMS announcement
An ICC-based CMM for color management
Brought to you by:
mm2
From: Marti.Maria <mar...@li...> - 2008-11-01 12:01:15
|
Dear Little CMS community: On a day like today, first preview of Little CMS library was released. Year was 1998. The library was still buggy and not completed, but the basic API was already defined and some functionality was there too. That means, today Little CMS is getting 10 years old!. I would like to thank all you for the incredible amount of support you have provided: reviewing the code and documentation, providing utilities, wrappers and programs based on the library and so on... the list of contributors is so big that would not fit this mail, thank you all! And of course, a 10th anniversary deserves some special. So, I have uploaded in the site a preview of the incoming LittleCMS 2.0, which is scheduled to be released Spring'09 http://www.littlecms.com/lcms-2.0preview-11-2-2008.zip This is an early preview, no documentation, just a couple of utilities, no build system, bugs, etc. *but*: the library code is complete. There is a extensive testbed too. Lcms-2.0 is almost a full rewrite. Here are some highlights on what is capable of: - Full V4 support, including Multi Processing elements. That means lcms2 will support any type of valid ICC profiles. - Floating point mode. That means there is a special mode for digital photo, math, etc. that has very high precision. - Plug-in support:. That means you can extend lcms to include private algorithms, like interpolation, new tags, new intents... SmartCMM mode is now supported across this feature. - Jan Morovic's Segment Maxima as gamut boundary descriptor. - Incomplete adaptation states for ICC-absolute colorimetric - Full support of all public tag types - Many other features. So, I would be glad to have any feedback from you. The mailing list seems a great way to post your thoughts. On the other hand, if you want to contact me in person, I will be giving a tutorial in the ICC DevCon 08 and co-chairing the interactive session of CIC16. If you are there, just let me know! All the best Marti Maria The LittleCMS project http://www.littlecms.com |
From: Boudewijn R. <bo...@va...> - 2008-11-01 12:24:34
|
On Saturday 01 November 2008, Marti.Maria wrote: > That means, today Little CMS is getting 10 years old!. Congratulations! Little CMS has been incredibly important for Krita, without lcms we wouldn't have gotten where we are now. Thanks! -- Boudewijn Rempt | http://www.valdyas.org |
From: Greg T. <gd...@ir...> - 2008-11-01 13:40:58
|
Understanding color management better has been on my todo list, and while I haven't really gotten to it, I want to say thank you for all your work and happy anniversary. I am currently the maintainer of the pkgsrc entry for lmcs (as graphics/lcms). pkgsrc is used on NetBSD and Dragonfly, and people also use it on other systems, perhaps most notably Solaris. On the web page you could add a link to www.pkgsrc.org with "(graphics/lcms)" after it. (I've done very little real work, so please don't credit me.) http://www.littlecms.com/lcms-2.0preview-11-2-2008.zip This is an early preview, no documentation, just a couple of utilities, no build system, bugs, etc. *but*: the library code is complete. There is a extensive testbed too. I don't know what you are thinking about build system. The way lcms 1.17 builds seems good to me -- autoconf is very portable, even if people think it's a bit crufty -- with windows on the side. More importantly, packaging systems support it, and I think ease of use by packaging systems is an important consideration, since most people run most software via packaging systems of some kind. There have been a number of build systems du jour, such as scons and cmake, and over the years I've come to believe that most of these are in practice less desirable because they don't have builtin support in all packaging systems. (Of course this is a difficult situation for improving build systems in general.) I consider myself competent autoconf/automake and will try to help out if you go that route and have issues. You didn't say if the published API and ABI will change. If the API changes, I'd strongly encourage you to use new names, perhaps liblcms2, so that old lcms and new lcms can both be installed. There will be a long period, perhaps a few years, over which depending programs change to lcms2, release new versions with the switch, and then those versions make it into packaging systems. Having both with different names means these switches can happen one at a time without needing synchronization, and that both versions can end up linked in the same program (for example if ufraw switches before gimp). FYI, here is the control file for pkgsrc, which is pleasingly small (a huge part of this is omitted because GNU_CONFIGURE=yes tells pkgsrc to call configure with the right options and that make/make install works as expected). I should reconsider the zlib situation (pkgsrc has a rule that packages should only depend on other things explicitly, so that binary packages work on other systems). ---------------------------------------- # $NetBSD: Makefile,v 1.26 2008/11/01 13:40:34 gdt Exp $ DISTNAME= lcms-1.17 PKGREVISION= 1 CATEGORIES= graphics MASTER_SITES= http://www.littlecms.com/ MAINTAINER= gdt@NetBSD.org HOMEPAGE= http://www.littlecms.com/ COMMENT= Little Color Management System -- a color management library PKG_INSTALLATION_TYPES= overwrite pkgviews PKG_DESTDIR_SUPPORT= user-destdir GNU_CONFIGURE= yes USE_LIBTOOL= yes TEST_TARGET= check # This is very MIT-like, but perhaps not the exact text. #LICENSE= lcms-license # lcms does not need zlib, but will look for it and link it to tifficc # if present. Therefore, we don't enjoin lcms from finding zlib, but # don't include it via bl3. # Avoid an ICE in gcc2 on sparc64 CONFIGURE_ENV+= F77=${FALSE:Q} PKGCONFIG_OVERRIDE= lcms.pc.in INSTALLATION_DIRS+= share/doc/lcms post-install: .for _f_ in LCMSAPI.TXT TUTORIAL.TXT ${INSTALL_DATA} ${WRKSRC}/doc/${_f_} ${DESTDIR}${PREFIX}/share/doc/lcms/${_f_} .endfor .include "../../graphics/jpeg/buildlink3.mk" .include "../../graphics/tiff/buildlink3.mk" .include "../../mk/bsd.pkg.mk" |
From: Bob F. <bfr...@si...> - 2008-11-01 15:09:33
|
On Sat, 1 Nov 2008, Greg Troxel wrote: > I am currently the maintainer of the pkgsrc entry for lmcs (as > graphics/lcms). pkgsrc is used on NetBSD and Dragonfly, and people also > use it on other systems, perhaps most notably Solaris. On the web page Lcms is included with quite a lot of systems but unfortunately many sytems don't keep it up to date as they should. One reason for this is that the maintainers don't know what lcms is and why it is important to keep it up to date. Pkgsrc is much quicker with updates than most other systems. > I don't know what you are thinking about build system. The way lcms > 1.17 builds seems good to me -- autoconf is very portable, even if I agree, although I am sure that I am biased. :-) > You didn't say if the published API and ABI will change. If the API > changes, I'd strongly encourage you to use new names, perhaps liblcms2, One change which has been promised is to stop using Windows typedefs in the code. Bob ====================================== Bob Friesenhahn bfr...@si..., http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ |
From: Cyrille B. <cb...@cb...> - 2008-11-02 10:16:24
|
First of all, congratulations for the ten years of LittleCMS and I see very interesting and exciting features for the 2.0 version ! On Saturday 01 November 2008, Greg Troxel wrote: > I don't know what you are thinking about build system. The way lcms > 1.17 builds seems good to me -- autoconf is very portable, even if > people think it's a bit crufty -- with windows on the side. Well that would be a big problem, wouldn't it ? Well of course, there is still the possibility to maintain different "project" files like it is done currently, but in my opinion that it is time best spend on more interesting things like code ;) > More > importantly, packaging systems support it, and I think ease of use by > packaging systems is an important consideration, since most people run > most software via packaging systems of some kind. There have been a > number of build systems du jour, such as scons and cmake, and over the > years I've come to believe that most of these are in practice less > desirable because they don't have builtin support in all packaging > systems. (Of course this is a difficult situation for improving build > systems in general.) That's hardly an argument against, otherwise, as you said, it would be impossible to make progress in any area. And I also think it's becoming less and less a problem, with some big open source project switching to cmake, I guess by now most packaging systems have support for it (at least on linux, and I bet BSDs are going to follow, after all NetBSD also have KDE, Scribus, inkscape which are big users of lcms which have (or are) switch(ing) to cmake ;) ). -- Cyrille Berger |
From: Hal V. E. <hv...@as...> - 2008-11-02 17:16:28
|
On Sunday 02 November 2008 02:16:10 Cyrille Berger wrote: > First of all, congratulations for the ten years of LittleCMS and I see very > interesting and exciting features for the 2.0 version ! > > On Saturday 01 November 2008, Greg Troxel wrote: > > I don't know what you are thinking about build system. The way lcms > > 1.17 builds seems good to me -- autoconf is very portable, even if > > people think it's a bit crufty -- with windows on the side. > > Well that would be a big problem, wouldn't it ? Well of course, there is > still the possibility to maintain different "project" files like it is done > currently, but in my opinion that it is time best spend on more interesting > things like code ;) > > > More > > importantly, packaging systems support it, and I think ease of use by > > packaging systems is an important consideration, since most people run > > most software via packaging systems of some kind. There have been a > > number of build systems du jour, such as scons and cmake, and over the > > years I've come to believe that most of these are in practice less > > desirable because they don't have builtin support in all packaging > > systems. (Of course this is a difficult situation for improving build > > systems in general.) > > That's hardly an argument against, otherwise, as you said, it would be > impossible to make progress in any area. And I also think it's becoming > less and less a problem, with some big open source project switching to > cmake, I guess by now most packaging systems have support for it (at least > on linux, and I bet BSDs are going to follow, after all NetBSD also have > KDE, Scribus, inkscape which are big users of lcms which have (or are) > switch(ing) to cmake ;) ). Along the sames lines LProf has been using scons but we are in transition to cmake. Our experience so far is that cmake is a very good cross platform build system and that it keeps getting better. It is definitely worth consideration. Hal |
From: Kai-Uwe B. <ku...@gm...> - 2008-11-01 15:45:11
|
Dear Marti, thanks for starting and developing this project and for continued sharing under a liberal license. Even if in the open source world not all features can yet be exployted, we enjoy littleCMS robustness and the ability to exchange with other platforms. The anouncement is worthy to the jubilee. kind regards Kai-Uwe Behrmann -- developing for colour management www.behrmann.name + www.oyranos.org |
From: Alastair M. R. <bla...@fa...> - 2008-11-01 17:05:09
|
Hi :) Marti.Maria wrote: > That means, today Little CMS is getting 10 years old!. I'd like to join with the chorus of thanks and congratulations for LCMS's 10th anniversary! PhotoPrint is another project which wouldn't exist without LCMS - so thank you! All the best, -- Alastair M. Robinson |
From: Hal V. E. <hv...@as...> - 2008-11-01 21:41:32
|
On Saturday 01 November 2008 05:00:16 Marti.Maria wrote: > Dear Little CMS community: > > On a day like today, first preview of Little CMS library was > released. Year was 1998. The library was still buggy and not > completed, but the basic API was already defined and some > functionality was there too. > > That means, today Little CMS is getting 10 years old!. > > I would like to thank all you for the incredible amount of support > you have provided: reviewing the code and documentation, > providing utilities, wrappers and programs based on the library > and so on... the list of contributors is so big that would not fit this > mail, thank you all! > > And of course, a 10th anniversary deserves some special. > > So, I have uploaded in the site a preview of the incoming > LittleCMS 2.0, which is scheduled to be released Spring'09 > > http://www.littlecms.com/lcms-2.0preview-11-2-2008.zip > > This is an early preview, no documentation, just a couple of > utilities, no build system, bugs, etc. *but*: the library code is > complete. There is a extensive testbed too. > > Lcms-2.0 is almost a full rewrite. Here are some highlights > on what is capable of: > > - Full V4 support, including Multi Processing elements. That > means lcms2 will support any type of valid ICC profiles. > - Floating point mode. That means there is a special mode for > digital photo, math, etc. that has very high precision. > - Plug-in support:. That means you can extend lcms to include > private algorithms, like interpolation, new tags, new intents... So this should allow for writing a plug-in to handle VCGT tags? Thanks I really wanted this feature and it will be very helpful. > SmartCMM mode is now supported across this feature. > - Jan Morovic's Segment Maxima as gamut boundary descriptor. > - Incomplete adaptation states for ICC-absolute colorimetric > - Full support of all public tag types > - Many other features. > > So, I would be glad to have any feedback from you. The > mailing list seems a great way to post your thoughts. On the > other hand, if you want to contact me in person, I will be giving > a tutorial in the ICC DevCon 08 and co-chairing the interactive > session of CIC16. If you are there, just let me know! > > All the best > Marti Maria > The LittleCMS project > http://www.littlecms.com > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge Build the coolest Linux based applications with Moblin SDK & win > great prizes Grand prize is a trip for two to an Open Source event anywhere > in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Lcms-user mailing list > Lcm...@li... > https://lists.sourceforge.net/lists/listinfo/lcms-user |
From: Guy K. K. <g....@ma...> - 2008-11-03 00:47:08
|
Hi Marti, thanks for the great effort you've put into this for the last 10 years, and thanks for showing the commitment for a (brighter) future with an upcoming 2.0 version. On Sun, 02 Nov 2008 01:00:16 Marti.Maria wrote: > So, I have uploaded in the site a preview of the incoming > LittleCMS 2.0, which is scheduled to be released Spring'09 > > http://www.littlecms.com/lcms-2.0preview-11-2-2008.zip I've downloaded. But how do you build it? I found only some junk for MS VisualWhatever, but no Makefile, autotools compatible files, README, etc. ... (BTW, I'm on a Linux system). I'd like to see if I can get my ctypes based bindings for Python working on this new code base as easily as I did on the 1.1.6 code base. Especially as I didn't see any SWIG code within the source tree, yet, either. Guy -- Guy K. Kloss Institute of Information and Mathematical Sciences Te Kura Putaiao o Mohiohio me Pangarau Room 2.63, Quad Block A Building Massey University, Auckland, Albany Private Bag 102 904, North Shore Mail Centre voice: +64 9 414-0800 ext. 9585 fax: +64 9 441-8181 eMail: G....@ma... http://iims.massey.ac.nz |
From: Tastl, I. <ing...@hp...> - 2008-11-03 21:45:14
|
Happy anniversary, Marti! Both the European version (www.hp.com/eur/longlasting-photos) and the North American version http://www.hp.com/go/printpermanence of the "HP Light Fade Simulator" use littlecms, which I trusted more than any other CMM. Kind regards, Inge Senior Color Scientist HP-Labs, Palo Alto, CA, USA -----Original Message----- From: Marti.Maria [mailto:mar...@li...] Sent: Saturday, November 01, 2008 5:00 AM To: Lcms List Subject: [Lcms-user] LittleCMS announcement Dear Little CMS community: On a day like today, first preview of Little CMS library was released. Year was 1998. The library was still buggy and not completed, but the basic API was already defined and some functionality was there too. That means, today Little CMS is getting 10 years old!. I would like to thank all you for the incredible amount of support you have provided: reviewing the code and documentation, providing utilities, wrappers and programs based on the library and so on... the list of contributors is so big that would not fit this mail, thank you all! And of course, a 10th anniversary deserves some special. So, I have uploaded in the site a preview of the incoming LittleCMS 2.0, which is scheduled to be released Spring'09 http://www.littlecms.com/lcms-2.0preview-11-2-2008.zip This is an early preview, no documentation, just a couple of utilities, no build system, bugs, etc. *but*: the library code is complete. There is a extensive testbed too. Lcms-2.0 is almost a full rewrite. Here are some highlights on what is capable of: - Full V4 support, including Multi Processing elements. That means lcms2 will support any type of valid ICC profiles. - Floating point mode. That means there is a special mode for digital photo, math, etc. that has very high precision. - Plug-in support:. That means you can extend lcms to include private algorithms, like interpolation, new tags, new intents... SmartCMM mode is now supported across this feature. - Jan Morovic's Segment Maxima as gamut boundary descriptor. - Incomplete adaptation states for ICC-absolute colorimetric - Full support of all public tag types - Many other features. So, I would be glad to have any feedback from you. The mailing list seems a great way to post your thoughts. On the other hand, if you want to contact me in person, I will be giving a tutorial in the ICC DevCon 08 and co-chairing the interactive session of CIC16. If you are there, just let me know! All the best Marti Maria The LittleCMS project http://www.littlecms.com ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Lcms-user mailing list Lcm...@li... https://lists.sourceforge.net/lists/listinfo/lcms-user |